From: llewelly@198.dsl.xmission.com
To: tmeged@nortelnetworks.com
Cc: help-gcc@gnu.org
Subject: Re: dwarf debug info for assembler
Date: Wed, 29 Dec 1999 01:26:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9912290224240.17559-100000@198.dsl.xmission.com> (raw)
In-Reply-To: <3869BE82.7910B376@ta-mail1.corpbni.baynetworks.com>
run
$info gcc
Then type 'gDebugging Options' . It will tab-complete for you.
If you don't have gcc's info pages, see
http://gcc.gnu.org/onlinedocs/gcc_2.html#SEC9
On Wed, 29 Dec 1999, Tal Meged wrote:
> Hi !
>
> I need to to compile an assembler source file with the dwarf debug flag,
> and
> I saw that it exists only for the C/C++ code. Do you know how can I
> append
> the dwarf inforamtion ?
>
WARNING: multiple messages have this Message-ID
From: llewelly@198.dsl.xmission.com
To: tmeged@nortelnetworks.com
Cc: help-gcc@gnu.org
Subject: Re: dwarf debug info for assembler
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9912290224240.17559-100000@198.dsl.xmission.com> (raw)
Message-ID: <19991231222400.VM1Vypw2-P1ffHhHfoS8Cvbh5RrNjmCEjM06Z1Dd3Co@z> (raw)
In-Reply-To: <3869BE82.7910B376@ta-mail1.corpbni.baynetworks.com>
run
$info gcc
Then type 'gDebugging Options' . It will tab-complete for you.
If you don't have gcc's info pages, see
http://gcc.gnu.org/onlinedocs/gcc_2.html#SEC9
On Wed, 29 Dec 1999, Tal Meged wrote:
> Hi !
>
> I need to to compile an assembler source file with the dwarf debug flag,
> and
> I saw that it exists only for the C/C++ code. Do you know how can I
> append
> the dwarf inforamtion ?
>
next prev parent reply other threads:[~1999-12-29 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-29 0:05 Tal Meged
1999-12-29 1:26 ` llewelly [this message]
1999-12-31 22:24 ` llewelly
1999-12-31 22:24 ` Tal Meged
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=Pine.LNX.4.10.9912290224240.17559-100000@198.dsl.xmission.com \
--to=llewelly@198.dsl.xmission.com \
--cc=help-gcc@gnu.org \
--cc=tmeged@nortelnetworks.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).