From: Daniel Jacobowitz <drow@false.org>
To: Kishore Paul <kishorep@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: vCont packets for next and step
Date: Tue, 13 Feb 2007 03:06:00 -0000 [thread overview]
Message-ID: <20070212220721.GA29749@caradoc.them.org> (raw)
In-Reply-To: <45D0E31E.8030802@freescale.com>
On Mon, Feb 12, 2007 at 03:58:54PM -0600, Kishore Paul wrote:
> Should the gdb host not be sending multiple vCont step packets for next,
> just like it does for step?
Yes. Are you sure those two were from the same location, i.e. in both
cases more than one step was necessary?
Failing that something may be wrong with your backtracing.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-12 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 21:42 Kishore Paul
2007-02-12 21:50 ` Daniel Jacobowitz
2007-02-12 22:07 ` Kishore Paul
2007-02-13 3:06 ` Daniel Jacobowitz [this message]
2007-02-13 3:25 ` Joel Brobecker
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=20070212220721.GA29749@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=kishorep@freescale.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