From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: DWARF question
Date: Wed, 26 Sep 2007 21:27:00 -0000 [thread overview]
Message-ID: <20070926212539.GA17502@caradoc.them.org> (raw)
In-Reply-To: <46FAC9D7.9080001@linux.vnet.ibm.com>
On Wed, Sep 26, 2007 at 06:06:31PM -0300, Carlos Eduardo Seo wrote:
> I found something strange in a binary generated from a fortran code: two
> compilation units for the same source file. Is that allowed by the DWARF
> specification? The binary was generated from a single source file.
Yes, it happens in several cases, though I don't know why in your case.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-26 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 21:25 Carlos Eduardo Seo
2007-09-26 21:27 ` Daniel Jacobowitz [this message]
2007-09-27 8:29 ` Carlos Eduardo Seo
2007-09-28 20:26 ` Carlos Eduardo Seo
2007-09-28 21:13 ` Jim Blandy
2007-09-28 23:14 ` Carlos Eduardo Seo
2007-09-28 23:49 ` Jim Blandy
2007-10-01 17:49 ` Carlos Eduardo Seo
2007-10-02 19:15 ` Jim Blandy
2007-10-02 19:26 ` Carlos Eduardo Seo
2007-10-02 21:43 ` Carlos Eduardo Seo
2007-10-02 23:05 ` Carlos Eduardo Seo
2007-10-02 20:03 ` Jim Blandy
2007-10-02 20:09 ` Jim Blandy
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=20070926212539.GA17502@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.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