From: Nick Clifton <nickc@cygnus.com>
To: ian@zembu.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: Patch: Support .loc STABS directive on ELF based toolchains.
Date: Thu, 30 Sep 1999 02:18:00 -0000 [thread overview]
Message-ID: <199909300918.KAA16033@pathia.cygnus.co.uk> (raw)
Hi Ian,
: We don't reject .loc outside of a .text section because we are
: mean-hearted. We reject it because it won't work. ECOFF debugging
: information builds a single table of line numbers for an object file.
: That table is implicitly assumed to be attached to the .text section.
: I don't see how to avoid that, given the weird construction of the
: ECOFF symbol table.
:
: If you want to use ECOFF debugging information, I think you need to
: avoid using linkonce sections. Or vice-versa. I recommend using
: straight stabs debugging information instead.
:
: If the debugging information really does work correctly, particularly
: after processing through ld -r, let me know (by work correctly, I mean
: that objdump -dl and gdb can correctly report line numbers for the
: linkonce functions in question).
You are right - it doesn't really work. I was fooled into believing
that it did because some line number information does get through into
the object file, but not the information for the constructors and
destructors.
I withdraw my patch and I will look to see if I can find a way for gcc
to workaround this.
Cheers
Nick
next reply other threads:[~1999-09-30 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-30 2:18 Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-29 7:37 Nick Clifton
1999-09-29 8:01 ` Ian Lance Taylor
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=199909300918.KAA16033@pathia.cygnus.co.uk \
--to=nickc@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.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).