Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>,
	Tom Tromey <tromey@redhat.com>
Subject: Re: [patch] Implement post_event for Python scripts.
Date: Wed, 18 Aug 2010 14:36:00 -0000	[thread overview]
Message-ID: <20100818143607.GA29823@caradoc.them.org> (raw)
In-Reply-To: <201008181445.52900.pedro@codesourcery.com>

On Wed, Aug 18, 2010 at 02:45:52PM +0100, Pedro Alves wrote:
> I'm also not sure whether ...
> 
> > /* We use a file handler, and not an async handler, so that we can
> >    wake up the main thread even when it is blocked in poll().  */
> > static int gdbpy_event_fds[2];
> 
> ... mingw-htep.c:gdb_select will be smart enough to apply the
> proper select for that file descriptor, or if we need to bring
> the whole patch in.

I think it'll work; it falls back to _get_osfhandle, So if you can
WaitForMultipleObjects on the Windows pipe handle, it'll do OK.  It
was just for some serial cases where you needed a separate handle that
we had problems.  OTOH if waiting for the pipe handle means you can
connect to it, or some other interpretation, we'll be back to the
beginning.  You could maybe adapt ser-pipe.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2010-08-18 14:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 18:53 Phil Muldoon
2010-07-20 19:08 ` Tom Tromey
2010-07-27 16:30 ` Joel Brobecker
2010-07-28 14:18   ` Phil Muldoon
2010-07-28 17:31     ` Joel Brobecker
2010-07-30 21:43       ` Tom Tromey
2010-08-03 14:26         ` Phil Muldoon
2010-08-03 17:00           ` Eli Zaretskii
2010-08-11 18:35           ` Tom Tromey
2010-08-11 19:05             ` Joel Brobecker
2010-08-11 21:08             ` Phil Muldoon
2010-07-28 17:49     ` Eli Zaretskii
2010-08-18 13:46 ` Pedro Alves
2010-08-18 14:36   ` Daniel Jacobowitz [this message]
2010-08-18 17:39     ` Pedro Alves
2010-08-18 18:13   ` Tom Tromey
2010-08-20  0:35     ` Pedro Alves

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=20100818143607.GA29823@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=pmuldoon@redhat.com \
    --cc=tromey@redhat.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