From: Ian Lance Taylor <ian@zembu.com>
To: nickc@cygnus.co.uk
Cc: binutils@sourceware.cygnus.com
Subject: Re: Patch: Support .loc STABS directive on ELF based toolchains.
Date: Wed, 29 Sep 1999 08:01:00 -0000 [thread overview]
Message-ID: <19990929150032.26734.qmail@daffy.airs.com> (raw)
In-Reply-To: <199909291437.PAA30604@pathia.cygnus.co.uk>
Date: Wed, 29 Sep 1999 15:37:42 +0100
From: Nick Clifton <nickc@cygnus.com>
Here is a small patch to allow the .loc STABS directive to be used
on ELF toolchains which use .gnu.linkonce.t sections as special
cases of the .text section.
1999-09-29 Nick Clifton <nickc@cygnus.com>
* ecoff.c (ecoff_directive_loc): Allow the .loc directive to
appear inside .gnu.linkoce.t. sections for ELF based
toolchains.
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).
! const char name[] = ".gnu.linkonce.t.";
I don't think K&R C compilers support automatic array initialization.
Make it static.
Ian
next prev parent reply other threads:[~1999-09-29 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 7:37 Nick Clifton
1999-09-29 8:01 ` Ian Lance Taylor [this message]
1999-09-30 2:18 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=19990929150032.26734.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=nickc@cygnus.co.uk \
/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).