From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver] Fix attaching notices
Date: Fri, 11 Jul 2008 14:13:00 -0000 [thread overview]
Message-ID: <20080711141326.GA5455@caradoc.them.org> (raw)
In-Reply-To: <200807080258.34187.pedro@codesourcery.com>
On Tue, Jul 08, 2008 at 02:58:33AM +0100, Pedro Alves wrote:
> > * infrun.c (handle_inferior_event): Do not ignore non-SIGSTOP while
> > attaching. Use signal_stop_state.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Bah.
> So, we either
>
> 1) go with my patch (on which the win32 part was a hack, but I
> can live with it), and live with the bogus notice
> against older gdbservers, or
>
> 2) change the test to:
>
> if (stop_soon == STOP_QUIETLY_NO_SIGSTOP
> && stop_signal == TARGET_SIGNAL_STOP
> && stop_signal == TARGET_SIGNAL_TRAP)
Ought to be some || in there :-)
> {
> stop_stepping (ecs);
> stop_signal = TARGET_SIGNAL_0;
> return;
> }
>
> Or even add a `&& stop_signal == TARGET_SIGNAL_0', and merge
> this stop_soon with STOP_QUIETLY_REMOTE.
I don't think I understand.
Allowing both stop and trap sounds reasonable to me. We already rely
on there not being other sources of SIGTRAP.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-11 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 23:26 Pedro Alves
2008-07-07 17:55 ` Daniel Jacobowitz
2008-07-07 23:52 ` Pedro Alves
2008-07-08 1:59 ` Pedro Alves
2008-07-11 14:13 ` Daniel Jacobowitz [this message]
2008-07-11 17:12 ` Pedro Alves
2008-07-11 17:37 ` Daniel Jacobowitz
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=20080711141326.GA5455@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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