From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: PATCH: propagate gdb host keyboard interrupts through gdbserver
Date: Wed, 11 Jul 2001 11:27:00 -0000 [thread overview]
Message-ID: <20010711112740.A22316@nevyn.them.org> (raw)
In-Reply-To: <5mzoabbbzd.fsf@jtc.redback.com>
On Wed, Jul 11, 2001 at 10:40:38AM -0700, J.T. Conklin wrote:
> I just committed the enclosed patch. It's a patch Greg McGary
> submitted all too long ago.
>
> I took the liberty of adding a comment explaining why code to ignore
> spurious interrupts was added. I also tweaked the change to input_-
> interrupt() to more closely resemble the original code.
>
> --jtc
>
> 2001-07-11 Greg McGary <greg@mcgary.org>
>
> * gdbserver/remote-utils.c (remote_open): Set gdbserver as "owner"
> of SIGIO.
> (input_interrupt): Don't block on read, in case we got redundant
> SIGIO. Don't gripe about redundant SIGIO.
> * gdbserver/low-hppabsd.c (mywait): Use waitpid(). Enable SIGIO
> handler while waiting.
> * gdbserver/low-linux.c (mywait): Likewise.
> * gdbserver/low-nbsd.c (mywait): Likewise.
> * gdbserver/low-sparc.c (mywait): Likewise.
What's the motivation for switching from wait to waitpid? When
gdbserver gains native thread support, we're going to be waiting for
more than one process at a time.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2001-07-11 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 10:40 J.T. Conklin
2001-07-11 11:27 ` Daniel Jacobowitz [this message]
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=20010711112740.A22316@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sourceware.cygnus.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