From: Cary Coutant <ccoutant@google.com>
To: Jason Molenda <jmolenda@apple.com>
Cc: dwarf-discuss@lists.dwarfstd.org, gcc@gcc.gnu.org,
gdb@sourceware.org, Doug Evans <dje@google.com>,
Paul Pluzhnikov <ppluzhnikov@google.com>,
Sterling Augustine <saugustine@google.com>
Subject: Re: RFC: DWARF Extensions for Separate Debug Info Files ("Fission")
Date: Fri, 23 Sep 2011 17:58:00 -0000 [thread overview]
Message-ID: <CAHACq4p5-EscmeTZ0giD+F2M0T7=S77FTpq8=a-4aoOVc9FX_A@mail.gmail.com> (raw)
In-Reply-To: <B6D4E49C-77EC-4BE7-8EAA-8897A4682F9F@apple.com>
> The Apple approach has both the features of the Sun/HP implementation as well as the ability to create a standalone debug info file.
Thanks for the clarifications. I based my comments on a description
you sent me a couple of years ago, and I apologize for any
oversimplifications I introduced.
> The compiler puts DWARF in the .o file, the linker adds some records in the executable which help us to understand where files/function/symbols landed in the final executable[1].
Did you intend to add a footnote?
> If the user runs our gdb or lldb on one of these binaries, the debugger will read the DWARF directly out of the .o files on the fly. Because the linker doesn't need to copy around/update/modify the DWARF, link times are very fast. If the developer decides to debug the program, no extra steps are required - the debugger can be started up & used with the debug info still in the .o files.
We're trying to achieve something very similar, but we have the
additional goal of separating the info from the .o files because of
our distributed build environment. I also wanted to attempt to
standardize the approach, instead of having each vendor go in separate
directions.
Thanks,
-cary
next prev parent reply other threads:[~2011-09-23 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 0:22 Cary Coutant
2011-09-23 2:36 ` Jason Molenda
2011-09-23 2:26 ` Paul Pluzhnikov
2011-09-23 17:58 ` Cary Coutant [this message]
2011-09-23 21:02 ` Jason Molenda
2011-09-23 21:35 ` [Dwarf-Discuss] " John DelSignore
2011-09-23 13:51 ` Jan Kratochvil
2011-09-23 17:50 ` Cary Coutant
2011-10-20 21:43 ` Tom Tromey
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='CAHACq4p5-EscmeTZ0giD+F2M0T7=S77FTpq8=a-4aoOVc9FX_A@mail.gmail.com' \
--to=ccoutant@google.com \
--cc=dje@google.com \
--cc=dwarf-discuss@lists.dwarfstd.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jmolenda@apple.com \
--cc=ppluzhnikov@google.com \
--cc=saugustine@google.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).