From: congli <congli.cn@gmail.com>
To: gdb@sourceware.org
Subject: Re: Why does gdb implement 'next' command with a series of "vCont;s"?
Date: Wed, 01 Aug 2007 01:26:00 -0000 [thread overview]
Message-ID: <4414a3a80707311826s686e8c36rd6a7d22e1007827a@mail.gmail.com> (raw)
I got it. Thanks!
> 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 reply other threads:[~2007-08-01 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 1:26 congli [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-30 8:14 congli
2007-07-30 6:40 congli
2007-07-30 19:47 ` 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=4414a3a80707311826s686e8c36rd6a7d22e1007827a@mail.gmail.com \
--to=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