From: jtc@redback.com (J.T. Conklin)
To: Todd Whitesel <toddpw@best.com>
Cc: ac131313@cygnus.com (Andrew Cagney), gdb@sourceware.cygnus.com
Subject: Re: SOFTWARE_SINGLE_STEP_P and multi-arch
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <5mae6eu17u.fsf@jtc.redback.com> (raw)
In-Reply-To: <200103210951.BAA06932@shell17.ba.best.com>
>>>>> "Todd" == Todd Whitesel <toddpw@best.com> writes:
Todd> Cleaning out my mailbox I discovered something from early December:
>> Hardware single step support (implied by
>> !TARGET_SOFTWARE_SINGLE_STEP_P()) is target and not ISA/ABI
>> dependant.
>>
>> Some ISAs might support hardware single step but the actual target
>> may not (lousy OS support, limited stub functionality)
Todd> I should also note that some ISAs might NOT support hardware
Todd> single step but the actual target DOES, because it is simulated
Todd> in software by the OS or stub.
Indeed. I think some of our existing targets assume "hardware" single
stepping when the ISA does not support it. So far, we have been lucky
that all the ROM monitors, ICEs, and remote stubs emulate single step
on those targets.
At least as far as the remote protocol is concerned, a debug agent
SHOULD support the single step command. If I could be assured that it
wouldn't break anything, I'd change that to a MUST. The latency of
having GDB do software single step makes debugging unpleasant.
Todd> All modern VxWorks targets support this, and step-range as well.
Todd> I expect that JTC's remote-wdb.c backend is using them.
Indeed it does.
--jtc
--
J.T. Conklin
RedBack Networks
prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 17:23 Andrew Cagney
2000-12-05 6:40 ` Richard Earnshaw
2000-12-05 15:24 ` J.T. Conklin
2001-03-21 15:59 ` Todd Whitesel
2001-03-21 15:59 ` J.T. Conklin [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=5mae6eu17u.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=toddpw@best.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).