From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: [patch] Fix handle_inferior_event nostop signal handling for threads
Date: Tue, 09 Mar 2004 16:41:00 -0000 [thread overview]
Message-ID: <20040309164100.GD27765@nevyn.them.org> (raw)
In-Reply-To: <20040307010654.GA10796@nevyn.them.org>
On Sat, Mar 06, 2004 at 08:06:54PM -0500, Daniel Jacobowitz wrote:
> Atsushi-san, could you verify that this patch still fixes your problem?
> I took a look at the #if 0 block, and that made me look at the surrounding
> code; I don't believe that a bit of it is necessary. If we switch "current"
> threads in response to this event, then all the following bits of
> handle_inferior_event should handle the current thread correctly.
>
> If this works for you I'll commit it to HEAD. I'm not sure if it's safe for
> the branch. No regressions on native i686-linux, and it fixes a quirk that
> the previous patch I sent you introduced (we could sometimes fail to print
> about a pass/print/nostop signal).
> 2004-03-06 Daniel Jacobowitz <drow@mvista.com>
>
> * infrun.c (handle_inferior_event): Remove short-circuit code for
> events in a different thread.
I've committed this for HEAD after retesting on i686-linux and
i686-linux/gdbserver.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: [patch] Fix handle_inferior_event nostop signal handling for threads
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040309164100.GD27765@nevyn.them.org> (raw)
Message-ID: <20040319000900.TjO_CzyeFFU0tbIRzU4ccy4wbG3G5EoTDrvgsEAa5W0@z> (raw)
In-Reply-To: <20040307010654.GA10796@nevyn.them.org>
On Sat, Mar 06, 2004 at 08:06:54PM -0500, Daniel Jacobowitz wrote:
> Atsushi-san, could you verify that this patch still fixes your problem?
> I took a look at the #if 0 block, and that made me look at the surrounding
> code; I don't believe that a bit of it is necessary. If we switch "current"
> threads in response to this event, then all the following bits of
> handle_inferior_event should handle the current thread correctly.
>
> If this works for you I'll commit it to HEAD. I'm not sure if it's safe for
> the branch. No regressions on native i686-linux, and it fixes a quirk that
> the previous patch I sent you introduced (we could sometimes fail to print
> about a pass/print/nostop signal).
> 2004-03-06 Daniel Jacobowitz <drow@mvista.com>
>
> * infrun.c (handle_inferior_event): Remove short-circuit code for
> events in a different thread.
I've committed this for HEAD after retesting on i686-linux and
i686-linux/gdbserver.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-09 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 1:06 Daniel Jacobowitz
2004-03-07 14:14 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-09 16:41 ` Daniel Jacobowitz [this message]
2004-03-10 1:28 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-10 2:57 ` Daniel Jacobowitz
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` 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=20040309164100.GD27765@nevyn.them.org \
--to=drow@false.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=gdb-patches@sources.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