From: Andrew Cagney <ac131313@cygnus.com>
To: Quality Quorum <qqi@theworld.com>
Cc: gdb@sources.redhat.com
Subject: Re: software single step - feature request
Date: Tue, 15 Jan 2002 08:21:00 -0000 [thread overview]
Message-ID: <3C445705.6070607@cygnus.com> (raw)
In-Reply-To: <Pine.SGI.4.40.0201150834470.8634263-100000@shell01.TheWorld.com>
> Hi,
>
>
> There are a few nits associated with soft single step support, which are
> easy to work around but annoying enough to justify a fix.
Your not alone. This is taken from gdbarch.sh:
# FIXME/cagney/2001-01-18: This should be split in two. A target method
that indicat
es if
# the target needs software single step. An ISA method to implement it.
#
# FIXME/cagney/2001-01-18: This should be replaced with something that
inserts breakp
oints
# using the breakpoint system instead of blatting memory directly (as
with rs6000).
#
# FIXME/cagney/2001-01-18: The logic is backwards. It should be asking
if the target
can
# single step. If not, then implement single step using breakpoints.
F:2:SOFTWARE_SINGLE_STEP:void:software_single_step:enum target_signal
sig, int insert
_breakpoints_p:sig, insert_breakpoints_p::0:0
> 1. Soft single step is configured per platform (e.g. arm-wince has one
> and generic arm does not), IMHO, it should be provided on per CPU
> basis.
>
> 2. It has to be provided for every CPU - may be as part of multi-arch
> transition.
>
> 3. It should be run-time configurable - so it should be possible to
> use the same gdb image both with and without soft single step.
>
> 4. If target supports hw single step it should be possible to configure
> removal of breakpoints before stepping.
>
>
> Thanks,
>
> Aleksey
see gdb/120
next prev parent reply other threads:[~2002-01-15 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 5:51 Quality Quorum
2002-01-15 8:21 ` Andrew Cagney [this message]
2002-01-15 10:13 ` Quality Quorum
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=3C445705.6070607@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=qqi@theworld.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