From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, dje@google.com, teawater@gmail.com, drow@false.org
Subject: Re: What about add a interface to output the assembly codes follow inferior execution
Date: Wed, 04 Mar 2009 22:10:00 -0000 [thread overview]
Message-ID: <uwsb5lz23.fsf@gnu.org> (raw)
In-Reply-To: <200903041920.51471.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Wed, 4 Mar 2009 19:20:50 +0000
> Cc: Doug Evans <dje@google.com>,
> teawater@gmail.com,
> drow@false.org
>
> show-opcodes suggests to me that we're doing to show raw, numeric
> opcodes, which IIUC, is not what is being suggested.
>
> "disassembly" suggests to me that we're doing to show
> assembly mneumonics, which I thought was what is being proposed.
Actually, what was suggested does both:
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>
This assembly codes is for line 26 printf ("a = %d b = %d c = %d\n", a, b, c);
next prev parent reply other threads:[~2009-03-04 22:10 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
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 [this message]
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=uwsb5lz23.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--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