GNU bug report logs - #10933
24.0.94; No output shown in *input/output* buffer of M-x gdb not working after first run

Previous Next

Full log

Message #18 received at 10933-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Troels Nielsen <bn.troels <at> gmail.com>
Cc: Rolando Pereira <ei08150 <at> fe.up.pt>, 10933-done <at> debbugs.gnu.org
Subject: Re: bug#10933: Acknowledgement (24.0.94;
	No output shown in *input/output* buffer of M-x gdb not working after
	first run)
Date: Fri, 23 Mar 2012 08:27:26 -0400

> I think this bug is due to gdb-mi creating a pty which it expects to
> remain open. When the process being debugged disconnects, emacs will
> receive an EIO-errno and (I believe mistakenly) send a SIGCHLD to
> itself, and stop listening to the pty.

> This patch fixes the problem for me.

Thanks, I don't understand what is special about gdb-mi that it's the
only one to trigger this problem, and I suspect there's a slightly
cleaner fix (as the above comment mentions, we only send ourselves
a SIGCHLD to work around problems we don't understand in some
undescribed situations, which may even be situations that don't exist
any more nowadays for all I know).
But I installed the patch anyway, with minor coding-convention cleanups
(wrap at 80 columns, space before open-paren).


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.