From: Andrew Cagney <ac131313@ges.redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] enable software single step on alpha-osf
Date: Mon, 05 Aug 2002 20:01:00 -0000 [thread overview]
Message-ID: <3D4F3C11.3000506@ges.redhat.com> (raw)
In-Reply-To: <20020805184920.GC892@gnat.com>
>> Can you confirm that the code is encountering a situtation where both
>> breakpoints_inserted and singlestep_breakpoints_inserted_p are true. I
>> think this occures when doing a single step after stepping off of a
>> breakpoint. When single stepping off a breakpoint, only
>> singlestep_breakpoints_inserted_p would be true.
>>
>> If this is the case then the comments should make mention of it. It
>> also makes the re-ordered if statement part of the patch correct.
>
>
> Yes, I can confirm this, and this should happen fairly often: suppose
> you have inserted a regular breakpoint in your program, anywhere, and
> then do a single step. Before resuming the inferior, GDB will re-insert
> the breakpoints, and set breakpoints_inserted. At the same time, because
> we are doing a s/w single step, singlestep_breakpoints_inserted_p will
> be set too. Did I miss something?
Thanks. No you didn't miss anything, I just want to be sure WFI is nasty.
The problem won't have been noticed previously as only the older targets
use software single-step and I don't know how often their testsuite is
beaten on.
> As for the re-ordering, I made it because I saw some regressions in the
> testsuite after switching to s/w single step. Unfortunately, I don't
> remember which ones, I would have to rerun the testsuite without this
> change to find them again. But the following comment explains in which
> cases the re-ordering was necessary:
Yes, ok, the part of the patch that re-orders the test is ok.
----
> I've tried as much as I can to make sure this can not happen, but I am
> not familiar enough to have a good level of confidence in my analysis.
> All I can say is: this patch fixes all the regressions observed in the
> testsuite after switching to software single step. I know this is no
> absolute proof, but that gives me a certain level of confidence.
BTW, if someone ever claims to have a ``good level of confidence'' in
that code, assume that they are lieing :-^
I'm still thinking about this bit, trying to find a way of not so much
increasing our confidence but at least putting us in a position where we
are more sure about what to do when we next encounter a problem.
Andrew
next prev parent reply other threads:[~2002-08-06 3:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 13:55 Joel Brobecker
2002-07-22 4:19 ` Eli Zaretskii
2002-07-25 16:38 ` Andrew Cagney
2002-07-26 10:17 ` Jason R Thorpe
2002-07-31 10:28 ` Joel Brobecker
2002-08-04 16:42 ` Andrew Cagney
2002-08-05 11:49 ` Joel Brobecker
2002-08-05 20:01 ` Andrew Cagney [this message]
2002-08-16 10:11 ` Andrew Cagney
2002-08-16 11:21 ` Joel Brobecker
2002-08-16 12:11 ` Andrew Cagney
2002-08-16 12:26 ` Daniel Jacobowitz
2002-08-16 12:40 ` Kevin Buettner
2002-08-16 14:40 ` Peter.Schauer
2002-08-16 12:41 ` Andrew Cagney
2002-08-16 16:05 ` Joel Brobecker
2002-08-16 16:45 ` Andrew Cagney
2002-08-16 17:58 ` Joel Brobecker
2002-08-16 18:23 ` Andrew Cagney
2002-08-16 23:29 ` Joel Brobecker
2002-08-20 8:55 ` Joel Brobecker
2002-08-20 17:29 ` Andrew Cagney
2002-08-20 19:14 ` Daniel Jacobowitz
2002-08-21 7:01 ` Joel Brobecker
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=3D4F3C11.3000506@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=brobecker@gnat.com \
--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