From: Vladimir Prus <vladimir@codesourcery.com>
To: Michael Snyder <msnyder@specifix.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't ignore consecutive breakpoints.
Date: Fri, 30 Nov 2007 10:04:00 -0000 [thread overview]
Message-ID: <200711301303.45966.vladimir@codesourcery.com> (raw)
In-Reply-To: <1196385275.2501.146.camel@localhost.localdomain>
On Friday 30 November 2007 04:14:35 Michael Snyder wrote:
> > > Can you test your patch on an architecture that uses software SS?
> >
> > I've tested on arm-linux/qemu, which uses software single-step,
> > and got no regressions.
> >
> > Looking again at the patch, the code fragment I'm changing has
> > two side-effects:
> >
> > - Setting ecs->random_signal
> > - Setting stop_bpstat
> >
> > My patch has no effect on the way ecs->random_signal is set.
> > However, in the case when we've just single-stepped over
> > breakpoint, the original code will clear stop_bpstat, and in
> > my patch, it would be set. We will immediately report report
> > the hit of the consecutive breakpoint. Since we don't set
> > ecs->another_trap, the trap_expected variable will be reset
> > to 0 when we resume.
> >
> > So, is the patch OK?
>
> Thanks for the testing and analysis.
> I have no further objection.
Thanks, checked in.
- Volodya
prev parent reply other threads:[~2007-11-30 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 20:10 Vladimir Prus
2007-11-26 18:51 ` Michael Snyder
2007-11-26 19:00 ` Vladimir Prus
2007-11-29 11:27 ` Vladimir Prus
2007-11-30 1:27 ` Michael Snyder
2007-11-30 10:04 ` Vladimir Prus [this message]
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=200711301303.45966.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@specifix.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