From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 9767@debbugs.gnu.org
Subject: bug#9767: 24.0.90; gdb initialization on Cygwin
Date: Wed, 19 Oct 2011 22:26:32 +0200 [thread overview]
Message-ID: <83ipnku3rb.fsf@gnu.org> (raw)
In-Reply-To: <4E9F2C49.4060307@cornell.edu>
> Date: Wed, 19 Oct 2011 16:00:09 -0400
> From: Ken Brown <kbrown@cornell.edu>
> CC: 9767@debbugs.gnu.org
>
> After M-x gdb finishes its initialization, emacs goes into its command
> loop. read_char calls sit_for with a timeout of 30 seconds, and sit_for
> calls wait_reading_process_output, which calls select. The call to
> select fails immediately with EINTR. I don't understand the command
> loop well enough to know what's interrupting the select call.
EINTR means that some signal arrived (assuming that Cygwin's `select'
is Posix-ish enough). The question is, which signal? Does Cygwin
provide any tools to see which signals were delivered to a program?
Also, the fact that `select' is interrupted doesn't necessarily mean
that the input arrival is ignored, does it? Doesn't
wait_reading_process_output loop around and examines the input
descriptors again? If not, why not? IOW, why should EINTR become a
failure?
> The code in keyboard.c is full of alarms and timers, presumably related
> to polling for keyboard input. Could this polling be doing something
> that interrupts the select call under some circumstances?
Atimers (those which are responsible for the "busy cursor" display)
could deliver SIGALRM, yes. But again, I don't see why this should
fail the loop that waits for input, and then only in this particular
case. Something else is at work here.
next prev parent reply other threads:[~2011-10-19 20:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 16:02 bug#9767: 24.0.90; gdb initialization on Cygwin Ken Brown
2011-10-16 23:08 ` Ken Brown
2011-10-17 5:39 ` Eli Zaretskii
2011-10-19 20:00 ` Ken Brown
2011-10-19 20:26 ` Eli Zaretskii [this message]
2011-10-19 20:43 ` Ken Brown
2011-10-19 21:03 ` Andreas Schwab
2011-10-19 22:02 ` Eli Zaretskii
2011-10-20 2:11 ` Ken Brown
2011-10-21 20:47 ` Ken Brown
2011-10-21 22:15 ` Eli Zaretskii
2011-10-22 9:51 ` Ken Brown
2011-10-22 20:58 ` Ken Brown
2011-10-23 21:59 ` Ken Brown
2011-10-21 22:24 ` Stefan Monnier
2011-10-22 9:47 ` Ken Brown
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=83ipnku3rb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9767@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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).