From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC][patch] Allow to disassemble line.
Date: Sat, 17 Oct 2009 15:50:00 -0000 [thread overview]
Message-ID: <8ac60eac0910170849p45d24187o449011fc0aa21fc7@mail.gmail.com> (raw)
In-Reply-To: <83zl7qh163.fsf@gnu.org>
On Sat, Oct 17, 2009 at 1:31 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 16 Oct 2009 16:11:27 -0700
>> From: Paul Pluzhnikov <ppluzhnikov@google.com>
>>
>> (top) set disassemble-next-line on
>> (top) ni
>> 0x000000000054d225 510 val = func (func_args);
>> 0x000000000054d221 <catch_errors+69>: 48 8b 7d d0 mov -0x30(%rbp),%rdi
>> * 0x000000000054d225 <catch_errors+73>: 48 8b 45 d8 mov -0x28(%rbp),%rax
>> 0x000000000054d229 <catch_errors+77>: ff d0 callq *%rax
>> 0x000000000054d22b <catch_errors+79>: 89 45 fc mov %eax,-0x4(%rbp)
>> (top) ni
>> 0x000000000054d229 510 val = func (func_args);
>> 0x000000000054d221 <catch_errors+69>: 48 8b 7d d0 mov -0x30(%rbp),%rdi
>> 0x000000000054d225 <catch_errors+73>: 48 8b 45 d8 mov -0x28(%rbp),%rax
>> * 0x000000000054d229 <catch_errors+77>: ff d0 callq *%rax
>> 0x000000000054d22b <catch_errors+79>: 89 45 fc mov %eax,-0x4(%rbp)
>
> The asterisk in both cases is on the same mnemonics, "callq *%rax".
It's the "leading asterisk" that is the marker here, and it moves from
0x000000000054d225 to 0x000000000054d229.
Instruction itself (which is "callq *%rax") is constant, just like it
should be.
Or did I misunderstand your question?
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-10-17 15:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 0:50 Paul Pluzhnikov
2009-10-02 6:52 ` Joel Brobecker
2009-10-02 18:31 ` Paul Pluzhnikov
2009-10-02 18:49 ` Joel Brobecker
2009-10-02 15:17 ` Tom Tromey
2009-10-08 16:16 ` Paul Pluzhnikov
2009-10-08 16:23 ` Daniel Jacobowitz
2009-10-08 16:25 ` Joel Brobecker
2009-10-08 16:52 ` Paul Pluzhnikov
2009-10-08 17:29 ` Daniel Jacobowitz
2009-10-08 17:33 ` Joel Brobecker
2009-10-16 23:07 ` Paul Pluzhnikov
2009-10-16 23:11 ` Paul Pluzhnikov
2009-10-17 8:33 ` Eli Zaretskii
2009-10-17 15:50 ` Paul Pluzhnikov [this message]
2009-10-17 16:49 ` Eli Zaretskii
2009-10-17 17:08 ` Paul Pluzhnikov
2009-10-17 19:55 ` Eli Zaretskii
2009-10-19 17:47 ` Tom Tromey
2009-10-19 18:09 ` Paul Pluzhnikov
2009-10-19 18:20 ` Paul Pluzhnikov
2009-10-19 18:30 ` Tom Tromey
2009-10-21 0:22 ` Paul Pluzhnikov
2009-10-21 4:07 ` Eli Zaretskii
2009-10-21 18:06 ` Paul Pluzhnikov
2009-10-21 18:16 ` Eli Zaretskii
2009-10-21 17:24 ` Tom Tromey
2009-10-19 18:49 ` Daniel Jacobowitz
2009-10-19 19:40 ` Joel Brobecker
2009-10-19 19:56 ` Daniel Jacobowitz
2009-10-19 20:03 ` Tom Tromey
2009-10-19 20:10 ` Joel Brobecker
2009-10-19 20:23 ` Paul Pluzhnikov
2009-10-19 20:47 ` Daniel Jacobowitz
2009-10-19 19:40 ` Eli Zaretskii
2009-10-19 19:55 ` Daniel Jacobowitz
2009-10-20 16:04 ` Tom Tromey
2009-10-08 16:24 ` Joel Brobecker
2009-10-08 17:16 ` Eli Zaretskii
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=8ac60eac0910170849p45d24187o449011fc0aa21fc7@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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