From: Daniel Jacobowitz <drow@false.org>
To: Chad Phillips <jcphillips@yahoo.com>
Cc: ramana.radhakrishnan@codito.com, gdb@sources.redhat.com
Subject: Re: single-stepping remote target fails
Date: Thu, 23 Jun 2005 19:13:00 -0000 [thread overview]
Message-ID: <20050623191246.GA23296@nevyn.them.org> (raw)
In-Reply-To: <42BAEC22.4010502@yahoo.com>
On Thu, Jun 23, 2005 at 01:06:42PM -0400, Chad Phillips wrote:
> Sending packet: $s#73...Ack
> Packet received: S00
> Sending packet: $p40#d4...Ack
> Packet received: 0000438E
>
> Program received signal 0, Signal 0.
You should be returning S05, SIGTRAP.
> GDB never sends a 'Z1' packet to set a hardware breakpoint as part of
> the step.
Why should it? Your stub claims to support hardware single step which
does not require a breakpoint.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-23 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 15:20 Chad Phillips
2005-06-23 15:25 ` Daniel Jacobowitz
2005-06-23 15:42 ` Chad Phillips
2005-06-23 16:16 ` Daniel Jacobowitz
2005-06-23 16:57 ` Ramana Radhakrishnan
2005-06-23 17:08 ` Chad Phillips
2005-06-23 19:13 ` Daniel Jacobowitz [this message]
2005-06-23 20:39 ` Chad Phillips
2005-06-23 20:43 ` 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=20050623191246.GA23296@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jcphillips@yahoo.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