unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christian Schwarzgruber <c.schwarzgruber.cs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [gdb(-mi)] Output of debugee not redirected to *input/output of ...* buffer when starting gdb via a script
Date: Mon, 25 Jan 2016 22:14:54 +0200	[thread overview]
Message-ID: <831t952z7l.fsf@gnu.org> (raw)
In-Reply-To: <87bn89bguw.fsf@gmail.com> (message from Christian Schwarzgruber on Mon, 25 Jan 2016 20:26:31 +0100)

> From: Christian Schwarzgruber <c.schwarzgruber.cs@gmail.com>
> Date: Mon, 25 Jan 2016 20:26:31 +0100
> 
> I have question about `gdb(-mi)' in emacs 24.5. I have written a bash debug
> wrapper script do choose between various front-ends and do some other stuff.
> When I do; M-x gdb RET; delete the default value; enter the script name along
> with the other optional parameters, and hit enter. Everything gets initialized
> successfully. Debugging the program works as well.
> 
> Example:
>   Run gdb (like this) dscript --cd=/path/to/the/executable executable ...
> 
> However, the output of the debugee gets not redirected to the *input/output of
> ...* buffer. Does someone know what the cause could be. Or how to further triage
> this problem/(bug?).
> 
> NOTE:
>   (gdb) show inferior-tty
>   shows the correct tty value, i.e. the tty of the *input/output of ...* buffer.

You didn't say what does your dscript do to run GDB.  It's hard to
answer your questions without knowing that.  For starters, does it
invoke GDB with the -i=mi command-line switch?  If not, that's your
first problem.

Also, if you invoke GDB directly like the default prompt suggests,
does the problem go away?



  reply	other threads:[~2016-01-25 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 19:26 [gdb(-mi)] Output of debugee not redirected to *input/output of ...* buffer when starting gdb via a script Christian Schwarzgruber
2016-01-25 20:14 ` Eli Zaretskii [this message]
2016-01-25 21:16   ` Christian Schwarzgruber
2016-01-26 15:44     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=831t952z7l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=c.schwarzgruber.cs@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).