From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PR threads/2015: Fix adjust_pc_after_break for thread debugging
Date: Wed, 28 Sep 2005 14:59:00 -0000 [thread overview]
Message-ID: <20050928145825.GA8872@nevyn.them.org> (raw)
In-Reply-To: <jefyrqglv7.fsf@sykes.suse.de>
On Wed, Sep 28, 2005 at 12:57:16AM +0200, Andreas Schwab wrote:
> Daniel Jacobowitz <drow@false.org> writes:
>
> > Which test failures are these? i.e. why doesn't anyone else see this
> > when they run the testsuite?
>
> I've somehow lost the log files and had to rerun the testsuite, and now I
> no longer see any difference in the test results.
>
> > Offhand I'd be suspicious that this helped - some other thread probably
> > needs its PC adjusted and now may not be.
>
> The patch will never result in less adjustments, because the other arm of
> the conditional will do the adjustment anyway if a breakpoint exists at
> the current PC. Note that prev_pc is also part of the thread context and
> may be wrong for the current thread as well.
Can you describe whatever testcase prompted you to make this change?
Is there some way we can reproduce the situation?
I've been looking this morning at a (probably unrelated) bug which
would probably vanish if this patch were applied, but which was really
triggered by an uninitialized variable in infrun. More to come once
I've tested.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-28 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 22:10 Andreas Schwab
2005-09-27 22:18 ` Mark Kettenis
2005-09-27 22:36 ` Andreas Schwab
2005-09-27 22:20 ` Daniel Jacobowitz
2005-09-27 22:24 ` Daniel Jacobowitz
2005-09-27 22:57 ` Andreas Schwab
2005-09-28 14:59 ` Daniel Jacobowitz [this message]
2005-09-28 15:47 ` Andreas Schwab
2005-09-28 15:51 ` Daniel Jacobowitz
2005-09-28 18:16 ` 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=20050928145825.GA8872@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@suse.de \
/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