From: Carlos Eduardo Seo <eduseo@br.ibm.com>
To: gdb@sourceware.org
Cc: drow@false.org
Subject: Re: DWARF question
Date: Thu, 27 Sep 2007 08:29:00 -0000 [thread overview]
Message-ID: <46FAD46B.9000006@br.ibm.com> (raw)
In-Reply-To: <20070926212539.GA17502@caradoc.them.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It's generating one compilation unit for the "main" program and another
one for a function called by that program. Both are implemented in the
same source file.
Carlos Eduardo Seo
Software Engineer
IBM Linux Technology Center
Phone: +55 19-2132-4339
T/L: 839-4339
E-Mail: eduseo@br.ibm.com
Daniel Jacobowitz wrote:
> 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.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+tRrkuArJ/wDsWwRAizRAKC801NR6yOlitCL2YD3WK0v2zN8mgCgucXp
wrd5czl6wJv5xIrZnKJr0VU=
=TvHT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-09-26 21:51 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
2007-09-27 8:29 ` Carlos Eduardo Seo [this message]
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=46FAD46B.9000006@br.ibm.com \
--to=eduseo@br.ibm.com \
--cc=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