From: Pierre Habraken <Pierre.Habraken@imag.fr>
To: "Keith.Walker" <Keith.Walker@arm.com>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Section .debug_info in object file
Date: Mon, 16 Sep 2002 03:43:00 -0000 [thread overview]
Message-ID: <3D85B5F5.403FA867@imag.fr> (raw)
In-Reply-To: <4.1.20020916105507.02b9c080@mhsun1.maidenhead.arm.com>
"Keith.Walker" wrote:
> [...]
> When the assembler is being invoked to assembler user supplied assembler
> files then the -gdwarf2 flag can be used to make the assembler generate the
> DWARF2 debugging information which describes the assembler file. [This
> is primarily the line to address table.] In this case it is the
> responsibility of the assembler to supply the DWARF2 information to
> describe the file being assembled.
Ok. So, I understand that this is a bug in Gnu As if the attribute
DW_AT_name is not added to the tag DW_TAG_compile_unit in the object
file...
Pierre
--
________________________________________________________________________
Pierre HABRAKEN - mailto:Pierre.Habraken@imag.fr
Tél: 04 76 82 72 83 - Fax: 04 76 82 72 87
IMAG-LSR BP72 38402 SAINT MARTIN D'HERES Cedex
________________________________________________________________________
next prev parent reply other threads:[~2002-09-16 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 2:42 Pierre Habraken
2002-09-12 4:46 ` Keith.Walker
2002-09-14 4:49 ` Pierre Habraken
2002-09-16 3:10 ` Keith.Walker
2002-09-16 3:30 ` Elias Athanasopoulos
2002-09-16 3:43 ` Pierre Habraken [this message]
2002-09-12 11:45 ` [PATCH] " Elias Athanasopoulos
2002-09-12 13:54 ` Richard Henderson
2002-09-12 14:55 ` Elias Athanasopoulos
2002-09-15 2:25 ` Elias Athanasopoulos
2002-09-16 19:35 ` Richard Henderson
2002-09-16 19:51 ` Richard Henderson
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=3D85B5F5.403FA867@imag.fr \
--to=pierre.habraken@imag.fr \
--cc=Keith.Walker@arm.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.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