unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Fredrik Tolf <fredrik@dolda2000.com>
To: help-gnu-emacs@gnu.org
Subject: GDB inferior I/O
Date: Tue, 29 Jul 2014 02:00:25 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1407290151170.31704@shack.dolda2000.com> (raw)

Dear list,

I only recently upgraded to Emacs 24 (since Debian Testing only recently 
did that). I'm generally positive about the changes, but there's one thing 
that irks me a bit, namely the new handling of I/O with inferior GDB 
processes.

As I'm sure you're aware, Emacs 23 handled I/O with the debugged program 
in the same buffer and with GDB itself, while Emacs 24 now handles it in a 
separate buffer. I have two problems with this:

  * It uses an extra window when debugging, where I'd rather use that space
    for other things.
  * It switches to that buffer whenever a program being debugged in the
    background decides to print something. Since I often have a server
    process running in GDB in the background that outputs log messages with
    a few millihertz or so, it springs up randomly every now and then.

I solved the latter problem with a simple modification to the 
gdb-inferior-filter function, but I'm still working on a solution to the 
former problem. It seems to me that I could simply remove the following 
three lines from gdb-init-1:

   (gdb-get-buffer-create 'gdb-inferior-io)
   (gdb-clear-inferior-io)
   (gdb-inferior-io--init-proc (get-process "gdb-inferior"))

I feel like this is likely to have unintended side-effects, however. Is it 
safe doing that, or will it confuse the communication with GDB somehow, or 
something?

If there's no problem with this, I'll make a more proper patch of it with 
customization later and submit it.

Thanks for reading!

--
Fredrik Tolf



                 reply	other threads:[~2014-07-29  0:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.DEB.2.10.1407290151170.31704@shack.dolda2000.com \
    --to=fredrik@dolda2000.com \
    --cc=help-gnu-emacs@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.
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).