From: Keith Owens <kaos@sgi.com>
To: Long Li <long21st@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: How to get the c source code in disassembly?
Date: Fri, 31 Jan 2003 11:27:34 +1100 [thread overview]
Message-ID: <27733.1043972854@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 30 Jan 2003 14:45:43 -0800." <20030130224543.7903.qmail@web40414.mail.yahoo.com>
On Thu, 30 Jan 2003 14:45:43 -0800 (PST),
Long Li <long21st@yahoo.com> wrote:
>I am having a problem with intermixing the C source
>code in the disassembly. I am using a MIPS
>crosscompiler on Redhat 7.1, gcc-3.0.4,
>binutils-2.11.2. When I compiled the C code, I added
>the -g option, and then use 'objdump -Sd' to get the
>disassembly. However, I did not see any C code mixed
>with the assembly, as said in the objdump manual when
>using -S option. Could you give me some help or
>suggestions?
objdump -S only works when the code is compiled with -g. And sometimes
not even then, objdump -S is flaky for ia64, although that could be the
old gcc/binutils I have to use :(.
prev parent reply other threads:[~2003-01-31 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 22:45 How to get the c source code in disassembly? Long Li
2003-01-31 0:27 ` Keith Owens [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=27733.1043972854@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.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