unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 9767@debbugs.gnu.org
Subject: bug#9767: 24.0.90; gdb initialization on Cygwin
Date: Thu, 20 Oct 2011 00:02:17 +0200	[thread overview]
Message-ID: <83fwiotzbq.fsf@gnu.org> (raw)
In-Reply-To: <m2d3ds4rtw.fsf@igel.home>

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,  9767@debbugs.gnu.org
> Date: Wed, 19 Oct 2011 23:03:23 +0200
> 
> Ken Brown <kbrown@cornell.edu> writes:
> 
> > No, wait_reading_process_output treats EINTR as though it meant there's no
> > input available.
> 
> Which is correct because an interrupted select does not report anything.
> And then the loop will be restarted to call select again.

Yes, that's what I thought should be happening.  Sorry if that was
unclear.

So the question is still why no input is being reported, although
wait_reading_process_output should loop and call `select' again.





  reply	other threads:[~2011-10-19 22:02 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
2011-10-19 20:43         ` Ken Brown
2011-10-19 21:03           ` Andreas Schwab
2011-10-19 22:02             ` Eli Zaretskii [this message]
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=83fwiotzbq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9767@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).