From: Yao Qi <yao@codesourcery.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How step over a ass call command?
Date: Tue, 07 Oct 2014 14:23:00 -0000 [thread overview]
Message-ID: <87r3ykt12e.fsf@codesourcery.com> (raw)
In-Reply-To: <CABrM6wnra-GjF0su9X1fZS7GqvuRJU9eHyt_9_AbQcU=kKgZAg@mail.gmail.com> (Peng Yu's message of "Sun, 5 Oct 2014 17:59:43 -0500")
Peng Yu <pengyu.ut@gmail.com> writes:
>>> Suppose that I use gdb with a binary file with source stripped.
What do you mean by "a binary file with source stripped"? Did you
compile without debug information? My gdb (built from current git repo
for x86-linux target) works correctly for binary without debug info.
(gdb) disassemble
Dump of assembler code for function main:
0x08048406 <+0>: push %ebp
0x08048407 <+1>: mov %esp,%ebp
=> 0x08048409 <+3>: call 0x8048400 <foo>
0x0804840e <+8>: mov $0x0,%eax
0x08048413 <+13>: pop %ebp
0x08048414 <+14>: ret
End of assembler dump.
(gdb) ni
0x0804840e in main ()
>> Try nexti, which is defined as
>> Execute one machine instruction, but if it is a function call, proceed
>> until the function returns
>
> I am sorry. I meant to say "nexti" in my original email. "nexti" seems
> to the same as "stepi" when the source code is stripped. Is it
> supposed to be so?
No, it looks a bug to me. What is your gdb version? or you can report
this bug here https://sourceware.org/bugzilla/
--
Yao (齐尧)
next prev parent reply other threads:[~2014-10-07 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 22:12 Peng Yu
2014-10-05 22:31 ` Max Filippov
2014-10-05 22:59 ` Peng Yu
2014-10-07 14:23 ` Yao Qi [this message]
2014-10-07 16:24 ` Pedro Alves
2014-10-07 16:26 ` Pedro Alves
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=87r3ykt12e.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=pengyu.ut@gmail.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