From: Pedro Alves <pedro@codesourcery.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] 09/10 Add "continue --all"
Date: Wed, 07 May 2008 19:36:00 -0000 [thread overview]
Message-ID: <200805071236.25860.pedro@codesourcery.com> (raw)
In-Reply-To: <007a01c8b01b$68103f80$3830be80$@u-strasbg.fr>
A Wednesday 07 May 2008 09:21:53, Pierre Muller wrote:
> I don't claim to understand this patch,
> but I am still curious about one point:
>
> why do you use TARGET_SIGNAL_0
> in proceed_ptid,
> while in non-stop mode, TARGET_SIGNAL_DEFAULT is used.
>
Because I copy&pasted it from somewhere else, and
didn't notice that. :-)
> If I understood correctly the code in
> proceed function from infrun.c,
> this would mean that in the non-stop mode with --all option,
> even if stop_signal was set to a value
> that is registered as "PASS",
> stop_signal would be reset and
> not passed to the inferior.
>
>
> Isn't that a misbehavior?
>
Thanks! That's indeed a bug.
> But anyway, should stop_signal become
> a threadvar, in the sense that it should
> be saved and restore in context_switch?
>
That's right. Not scritly command-per-thread related, but it
was taken care of in patch 4.
--
Pedro Alves
next prev parent reply other threads:[~2008-05-07 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 18:12 Pedro Alves
2008-05-07 11:58 ` Pierre Muller
2008-05-07 19:36 ` Pedro Alves [this message]
2008-05-08 18:29 ` Eli Zaretskii
2008-05-09 2:35 ` Pedro Alves
2008-05-09 3:08 ` Daniel Jacobowitz
2008-05-09 3:54 ` Pedro Alves
2008-05-09 17:07 ` Pedro Alves
2008-05-09 19:08 ` Daniel Jacobowitz
2008-05-09 19:20 ` Andrew STUBBS
2008-05-11 20:34 ` Joel Brobecker
2008-05-19 17:07 ` Pedro Alves
2008-05-19 21:29 ` Michael Snyder
2008-05-19 21:55 ` Daniel Jacobowitz
2008-05-19 22:46 ` Andreas Schwab
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=200805071236.25860.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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