From: Daniel Jacobowitz <drow@false.org>
To: "Decker, Paul" <Paul.Decker@analog.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>,
gdb@sources.redhat.com, amit bhor <amit.bhor@codito.com>
Subject: Re: RFC : Handling breakpoints on archs. with imprecise exceptions.
Date: Thu, 24 Mar 2005 23:32:00 -0000 [thread overview]
Message-ID: <20050324233231.GA13653@nevyn.them.org> (raw)
In-Reply-To: <E21A9A52FF03B249B20F0DC563DEBB311729688A@nwd2exm3.ad.analog.com>
On Thu, Mar 24, 2005 at 05:52:07PM -0500, Decker, Paul wrote:
> Hi all,
>
> Could you just save and restore 4 instructions for each breakpoint, and
> have a jump back to the original breakpoint address minus 1?
No. For instance, you will now hit the breakpoint if an instruction
two later in the stream is a branch target. Using more than one
instruction for a breakpoint is a real losing proposition.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-24 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 23:31 Decker, Paul
2005-03-24 23:32 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 19:46 Ramana Radhakrishnan
2005-03-24 19:57 ` Paul Gilliam
2005-03-24 20:23 ` Ramana Radhakrishnan
2005-03-24 21:46 ` Paul Gilliam
2005-03-24 20:37 ` Daniel Jacobowitz
2005-03-24 22:46 ` Ramana Radhakrishnan
2005-03-24 21:30 ` Kevin Buettner
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=20050324233231.GA13653@nevyn.them.org \
--to=drow@false.org \
--cc=Paul.Decker@analog.com \
--cc=amit.bhor@codito.com \
--cc=gdb@sources.redhat.com \
--cc=ramana.radhakrishnan@codito.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).