Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: RFA: Various Windows (mingw32) additions, mostly relating to select or serial ports
Date: Sat, 04 Feb 2006 15:23:00 -0000	[thread overview]
Message-ID: <uslqzjgg5.fsf@gnu.org> (raw)
In-Reply-To: <20060204151124.GD17011@nevyn.them.org> (message from Daniel 	Jacobowitz on Sat, 4 Feb 2006 10:11:24 -0500)

> Date: Sat, 4 Feb 2006 10:11:24 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> The problem is that, yes, all these objects are HANDLEs, and
> WaitForMultipleObjects can wait for many kinds of HANDLEs.  But there's
> different things that "waiting for a handle" might mean, and it doesn't
> happen to pick the right one.  So what I'm doing is using other
> handles, controlled by threads or async I/O functions, to signal the
> conditions we're interested in.

Thanks for the explanations.  It sounds like there's no way to do this
significantly better than you did.  So I'm satisfied and think that
your patches can go in (modulo the on-going discussion of where to put
them).

Out of curiosity: does Cygwin's `select' use a similar object-specific
code to handle different types of handles?

> > ...I don't think you included this entry.
> 
> Oops.  I added it while I was writing that bullet point.
> 
> +* Improved Windows host support
> +
> +GDB now builds as a cross debugger hosted on i686-mingw32, including
> +native console support, and remote communications using either
> +network sockets or serial ports.

Thanks.  I think this is good.


  reply	other threads:[~2006-02-04 15:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 22:05 Daniel Jacobowitz
2006-02-03 22:08 ` Daniel Jacobowitz
2006-02-04 12:43   ` Eli Zaretskii
2006-02-04 15:13     ` Daniel Jacobowitz
2006-02-04  6:28 ` Ian Lance Taylor
2006-02-04 10:30   ` Eli Zaretskii
2006-02-04 17:06     ` Ian Lance Taylor
2006-02-04 17:45       ` Eli Zaretskii
2006-02-04 15:00   ` Daniel Jacobowitz
2006-02-05  0:01     ` Ian Lance Taylor
2006-02-05 22:00       ` Daniel Jacobowitz
2006-02-06  3:27         ` Ian Lance Taylor
2006-02-06  4:03           ` Daniel Jacobowitz
2006-02-04 12:38 ` Eli Zaretskii
2006-02-04 15:11   ` Daniel Jacobowitz
2006-02-04 15:23     ` Eli Zaretskii [this message]
2006-02-04 15:30       ` Daniel Jacobowitz
2006-02-06 21:02 ` Daniel Jacobowitz
2006-02-06 23:02   ` Mark Kettenis
2006-02-06 23:17     ` Daniel Jacobowitz
2006-02-06 23:21     ` Christopher Faylor
2006-02-09 22:38     ` Daniel Jacobowitz
2006-02-10  7:53       ` Eli Zaretskii
2006-02-10 20:46       ` Mark Kettenis
2006-02-10 22:02         ` Daniel Jacobowitz
2006-02-07  4:41   ` Eli Zaretskii

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=uslqzjgg5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox