From: "Dave Korn" <dave.korn@artimi.com>
To: "'Simon Richter'" <Simon.Richter@hogyros.de>
Cc: "'Daniel Jacobowitz'" <drow@false.org>,
"'Efim Monjak'" <ymonyak@lipowsky.de>, <gdb@sources.redhat.com>
Subject: RE: break of close loop
Date: Fri, 04 Nov 2005 15:35:00 -0000 [thread overview]
Message-ID: <SERRANOebmspH2q6Dqa00000176@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <436B7BE1.5040702@hogyros.de>
Simon Richter wrote:
> Hi,
>
> Dave Korn wrote:
>
>> The stub is probably implemented by placing a temp breakpoint
>> immediately after the instruction to be tested, but has negelected the
>> fact that to handle jumps you may need to place the temp breakpoint
>> somewhere _other_ than immediately after the instruction,
>
> The question at hand appears to be breakpoints placed on top of the
> instruction being stepped, as the instruction steps back to itself. This
> is especially common on architectures with a dedicated "decrement and
> jump if not zero" instruction.
That's one of the corner-cases and is indeed one of the reasons why
emulating a branch instruction is often a better idea than trying to let it
run and trap it....
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-11-04 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 9:15 Efim Monjak
2005-11-04 14:27 ` Daniel Jacobowitz
2005-11-04 15:13 ` Dave Korn
2005-11-04 15:19 ` Simon Richter
2005-11-04 15:35 ` Dave Korn [this message]
2005-11-04 15:39 ` 'Daniel Jacobowitz'
2005-11-04 15:46 ` Dave Korn
2005-11-04 16:00 ` 'Daniel Jacobowitz'
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 16:41 Efim Monjak
2005-11-03 21:25 ` 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=SERRANOebmspH2q6Dqa00000176@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=Simon.Richter@hogyros.de \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ymonyak@lipowsky.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).