From: Ken Mandelberg <km@mathcs.emory.edu>
To: gdb@sourceware.org
Subject: Re: Remote Debugging with NEXT Command
Date: Wed, 11 Jun 2014 15:24:00 -0000 [thread overview]
Message-ID: <539874B0.80009@mathcs.emory.edu> (raw)
In-Reply-To: <EB3B29AD43CA924DA27099BC85192376E0FAEA5C@EU-MBX-02.mgc.mentorg.com>
Thanks all!
We had missed taking advantage of range stepping in the stub, and not
used the vCont packet. It's made all the difference for NEXT.
next prev parent reply other threads:[~2014-06-11 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 21:02 Ken Mandelberg
2014-06-10 21:13 ` Paul_Koning
2014-06-10 21:21 ` Ken Mandelberg
2014-06-11 10:01 ` Abid, Hafiz
2014-06-11 15:24 ` Ken Mandelberg [this message]
2014-06-11 10:26 ` Luis Machado
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=539874B0.80009@mathcs.emory.edu \
--to=km@mathcs.emory.edu \
--cc=gdb@sourceware.org \
/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