From: Doug Evans <dje@google.com>
To: teawater <teawater@gmail.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: What about add a interface to output the assembly codes follow inferior execution
Date: Tue, 03 Mar 2009 16:42:00 -0000 [thread overview]
Message-ID: <e394668d0903030841wa3bfef8udd9c5e667d0c0f1e@mail.gmail.com> (raw)
In-Reply-To: <daef60380903021910w3d4e7f0w76f8b732aaa46c37@mail.gmail.com>
On Mon, Mar 2, 2009 at 7:10 PM, teawater <teawater@gmail.com> wrote:
> Hi guys,
>
> I am not sure gdb have a interface to output assembly codes except
> "disassemble".
> Maybe gdb can support a interface can output assembly codes of next
> part of code.
>
> For example:
> #If exec-disassemble set to auto, just output assembly codes if there
> is not line message.
> #It will be the default value.
> (gdb) set exec-disassemble auto
> (gdb) si
> 0x080483ee 24 b = printf ("a = %d b = %d c = %d\n", a, b, c);
> (gdb) si
> 0x080482d8 in printf@plt ()
> Current language: auto; currently asm
> 0x080482d8 <printf@plt+0>: jmp *0x8049670
> (gdb) si
> 0x080482de in printf@plt ()
> 0x080482de <printf@plt+6>: push $0x10
>
> #If exec-disassemble set to on, gdb will always output assembly codes.
> (gdb) set exec-disassemble on
> (gdb) n
> 26 printf ("a = %d b = %d c = %d\n", a, b, c);
> 80483fe: 8b 15 84 96 04 08 mov 0x8049684,%edx
> 8048404: 8b 45 f4 mov -0xc(%ebp),%eax
> 8048407: 89 44 24 0c mov %eax,0xc(%esp)
> 804840b: 8b 45 f8 mov -0x8(%ebp),%eax
> 804840e: 89 44 24 08 mov %eax,0x8(%esp)
> 8048412: 89 54 24 04 mov %edx,0x4(%esp)
> 8048416: c7 04 24 58 85 04 08 movl $0x8048558,(%esp)
> 804841d: e8 b6 fe ff ff call 80482d8 <printf@plt>
>
> #If exec-disassemble set to off, gdb will work like before.
> (gdb) set exec-disassemble off
>
>
> What do you think about it?
Are you looking for behaviour different than what "disp/8i $pc" would give you?
next prev parent reply other threads:[~2009-03-03 16:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 3:11 teawater
2009-03-03 16:42 ` Doug Evans [this message]
2009-03-03 17:04 ` Daniel Jacobowitz
2009-03-04 2:29 ` teawater
2009-03-04 4:09 ` Eli Zaretskii
2009-03-04 5:30 ` teawater
2009-03-04 17:15 ` Doug Evans
2009-03-04 19:09 ` Eli Zaretskii
2009-03-04 19:20 ` Pedro Alves
2009-03-04 22:10 ` Eli Zaretskii
2009-03-04 19:24 ` Doug Evans
2009-03-04 19:26 ` Daniel Jacobowitz
2009-03-04 19:32 ` Pedro Alves
2009-03-04 21:25 ` Doug Evans
2009-03-04 22:14 ` Eli Zaretskii
2009-03-04 22:20 ` Pedro Alves
2009-03-04 22:31 ` Doug Evans
2009-03-04 23:41 ` Tom Tromey
2009-03-05 2:42 ` teawater
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=e394668d0903030841wa3bfef8udd9c5e667d0c0f1e@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=teawater@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