From: Bart Trojanowski <bart@jukie.net>
To: Kallol Biswas <kallol@efi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: C source lines for assembly listing
Date: Sat, 19 Jan 2002 22:14:28 -0500 [thread overview]
Message-ID: <20020119221428.O18844@jukie.net> (raw)
In-Reply-To: <Pine.LNX.4.40L0.0201170137380.32025-100000@karma.oltrelinux.com> <3C462ACD.5F61BFDC@efi.com>
In-Reply-To: <3C462ACD.5F61BFDC@efi.com>; from kallol@efi.com on Wed, Jan 16, 2002 at 05:37:17PM -0800
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
* Kallol Biswas <kallol@efi.com> [020116 20:35]:
> Hi,
> Does gcc have an option to list the C source line information for
> assembly instructions?
I am not sure what you are asking for... but I will give it a shot. ;)
One of the tools that comes with the package binutils is called objdump.
If you compile your source with -g flag then you can use objdump to
display mixed assembly and C source code.
gcc -g foo.c -o foo.o
objdumpt -S foo.o
I hope this helps.
B.
--
WebSig: http://www.jukie.net/~bart/sig/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-01-20 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 1:16 Rik spreading bullshit about VM Andrea Scrimieri
2002-01-17 1:37 ` C source lines for assembly listing Kallol Biswas
2002-01-20 3:14 ` Bart Trojanowski [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=20020119221428.O18844@jukie.net \
--to=bart@jukie.net \
--cc=kallol@efi.com \
--cc=linux-kernel@vger.kernel.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