From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: "disassemble" shows code, but not with /m
Date: Wed, 19 Mar 2014 19:04:00 -0000 [thread overview]
Message-ID: <83txau80wx.fsf@gnu.org> (raw)
In-Reply-To: <20140319184506.GA25053@host2.jankratochvil.net>
> Date: Wed, 19 Mar 2014 19:45:06 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb@sourceware.org
>
> On Wed, 19 Mar 2014 18:50:22 +0100, Eli Zaretskii wrote:
> > IOW, the /m switch somehow inhibits the disassembly.
>
> The /m switch is broken for -O2 -g code even if it prints something:
That executable is compiled with -O0, not -O2. Sorry I didn't mention
that.
Also, the /m switch does work for functions not declared inline in the
same executable.
> http://sourceware.org/bugzilla/show_bug.cgi?id=11833
That bug does not show such a complete failure to disassembly that I
experienced.
> Use objdump -dS in these cases - that one works
> (although I prefer rather objdump -dl for -O2 -g cases).
Thanks for the tip.
> /m is dependent on .debug_line which I guess is not right in your inferior.
Why not? it has DWARF2 debug info.
prev parent reply other threads:[~2014-03-19 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 17:50 Eli Zaretskii
2014-03-19 18:45 ` Jan Kratochvil
2014-03-19 19:04 ` Eli Zaretskii [this message]
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=83txau80wx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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