From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Troels Nielsen <bn.troels@gmail.com>
Cc: Rolando Pereira <ei08150@fe.up.pt>, 10933-done@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <jwvwr6bmrpj.fsf-monnier+gnus-read-ephemeral-bug@gnu.org> (raw)
In-Reply-To: <CAOdE5WRWaUpEc03OULtvyX9OC2tc=rm-s8xhhgnLOfs9C=g29w@mail.gmail.com> (Troels Nielsen's message of "Thu, 22 Mar 2012 10:30:32 +0100")
> 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
prev parent reply other threads:[~2012-03-23 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 23:29 bug#10933: 24.0.94; No output shown in *input/output* buffer of M-x gdb not working after first run Rolando Pereira
[not found] ` <handler.10933.B.133081746410377.ack@debbugs.gnu.org>
2012-03-05 0:09 ` bug#10933: Acknowledgement (24.0.94; No output shown in *input/output* buffer of M-x gdb not working after first run) Rolando Pereira
2012-03-22 9:30 ` Troels Nielsen
2012-03-23 12:27 ` Stefan Monnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvwr6bmrpj.fsf-monnier+gnus-read-ephemeral-bug@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=10933-done@debbugs.gnu.org \
--cc=bn.troels@gmail.com \
--cc=ei08150@fe.up.pt \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.