From: Daniel Jacobowitz <drow@false.org>
To: congli <congli.cn@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Why does gdb implement 'next' command with a series of "vCont;s"?
Date: Mon, 30 Jul 2007 19:47:00 -0000 [thread overview]
Message-ID: <20070730114303.GA25571@caradoc.them.org> (raw)
In-Reply-To: <4414a3a80707292237l543b1b03w5cc2d5d93fe44a47@mail.gmail.com>
On Mon, Jul 30, 2007 at 01:37:33PM +0800, congli wrote:
> My question is, when I issue the 'next' command, gdb already
> know the 'step_range_end' is 0x804836f, why not implement the
> 'next' command by set a breakpoint at 0x804836f and then issue
> "vCont;c"? When the program meet the breakpoint at 0x804836f,
> we can do a single "vCont;s" to the first instruction of
> line 7, 0x8048372.
GDB does not know what the instructions between here and there do.
One of them might be a branch or a function call.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-30 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 6:40 congli
2007-07-30 19:47 ` Daniel Jacobowitz [this message]
2007-07-30 8:14 congli
2007-08-01 1:26 congli
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=20070730114303.GA25571@caradoc.them.org \
--to=drow@false.org \
--cc=congli.cn@gmail.com \
--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