From: James Cownie <jcownie@etnus.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Nick Clifton <nickc@redhat.com>, Ian Lance Taylor <ian@airs.com>,
Andy Chittenden <AChittenden@bluearc.com>,
binutils@sourceware.org, Martin Dorey <mdorey@bluearc.com>
Subject: Re: excessive stab information
Date: Tue, 19 Apr 2005 16:27:00 -0000 [thread overview]
Message-ID: <20050419162728.9B36BA993@amd64.cownie.net> (raw)
In-Reply-To: Your message of "19 Apr 2005 16:17:30 -0000." <1113927450.6799.ezmlm@sources.redhat.com>
> That's not quite the same thing; this links debug information into the
> executable, then copies it elsewhere. Ian's describing an approach of
> leaving the debug info in unlinked object files and then referencing it
> from the executable - never including it at all.
>
> I believe Sun's compiler does this.
Sun do it with Stabs (see the .stabs.index section and related
documentation).
HP do it on HPUX with DWARF (which requires some additional linker magic
and sections to allow you to work out which object file any chunk of any
output section came from).
--
-- Jim
--
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com
next parent reply other threads:[~2005-04-19 16:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1113927450.6799.ezmlm@sources.redhat.com>
2005-04-19 16:27 ` James Cownie [this message]
2005-04-29 8:13 Andy Chittenden
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 16:58 Andy Chittenden
2005-04-28 17:02 ` Dave Korn
2005-04-28 16:48 Andy Chittenden
2005-04-28 16:53 ` Dave Korn
2005-04-28 16:02 Andy Chittenden
2005-04-28 16:32 ` Dave Korn
2005-04-28 15:42 Andy Chittenden
2005-04-28 15:50 ` Dave Korn
2005-04-28 16:27 ` Ian Lance Taylor
2005-04-28 15:21 Andy Chittenden
2005-04-28 15:34 ` Ian Lance Taylor
2005-04-28 15:41 ` Daniel Jacobowitz
2005-04-20 16:16 Andy Chittenden
2005-04-20 16:24 ` Dave Korn
2005-04-20 9:29 Andy Chittenden
2005-04-20 14:59 ` Ian Lance Taylor
2005-04-19 9:38 Andy Chittenden
2005-04-18 16:39 Andy Chittenden
2005-04-18 17:13 ` Ian Lance Taylor
2005-04-18 14:53 Andy Chittenden
2005-04-18 15:11 ` Ian Lance Taylor
2005-04-18 14:26 Jan Beulich
2005-04-18 14:28 ` Daniel Jacobowitz
2005-04-18 12:44 Andy Chittenden
2005-04-18 14:04 ` Ian Lance Taylor
2005-04-19 11:44 ` Nick Clifton
2005-04-19 13:04 ` Daniel Jacobowitz
2005-04-19 14:51 ` Nick Clifton
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=20050419162728.9B36BA993@amd64.cownie.net \
--to=jcownie@etnus.com \
--cc=AChittenden@bluearc.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=ian@airs.com \
--cc=mdorey@bluearc.com \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).