Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: Masaki Muranaka <monaka@monami-software.com>,
		gdb-patches@sourceware.org
Subject: Re: [patch] Crashed cross gdb/MinGW host
Date: Sat, 10 Jun 2006 20:41:00 -0000	[thread overview]
Message-ID: <20060610204133.GC324@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20060610182507.GA802@nevyn.them.org>

On Sat, Jun 10, 2006 at 02:25:07PM -0400, Daniel Jacobowitz wrote:
>On Fri, May 19, 2006 at 02:52:57PM -0400, Christopher Faylor wrote:
>> On Fri, May 19, 2006 at 06:47:04PM +0900, Masaki Muranaka wrote:
>> >My sh-elf-gdb on MinGW host was crashed when I tried to debug using the
>> >serial connection.  Here is a patch.
>> >
>> >It's possible the another plan to remove writefds check.  There is no
>> >support yet for writefds.
>> 
>> If this is truly supposed to be an emulation of the system select(), I
>> think it would make sense to check both !readfds and !writefds.
>
>Sorry for letting this sit so long.  I just encountered this bug today. 
>I think I tested console and pipe when I last touched this code
>but failed to test ser-base.
>
>The underlying problem is actually different.  The code looks like
>this:
>      if (!FD_ISSET (fd, readfds) && !FD_ISSET (fd, writefds))
>        continue;
>
>      if (FD_ISSET (fd, readfds))
>	...
>
>      if (FD_ISSET (fd, exceptfds))
>	...
>
>See the mismatch? :-(

I saw it and was wondering about it.  I'm glad to see consistency restored.

:-)

cgf


  reply	other threads:[~2006-06-10 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 10:45 Masaki Muranaka
2006-05-19 20:46 ` Christopher Faylor
2006-05-20  1:14   ` Masaki Muranaka
2006-06-10 18:25   ` Daniel Jacobowitz
2006-06-10 20:41     ` Christopher Faylor [this message]
2006-06-11 10:00     ` Masaki Muranaka

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=20060610204133.GC324@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.com \
    /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