From: Ian Lance Taylor <ian@zembu.com>
To: kevinb@cygnus.com, drepper@cygnus.com, rth@cygnus.com
Cc: gdb@sourceware.cygnus.com, binutils@sourceware.cygnus.com,
jimb@cygnus.com
Subject: Re: Zero valued N_FUN stabs in shared objects: Why?
Date: Fri, 10 Sep 1999 16:51:00 -0000 [thread overview]
Message-ID: <19990910234925.15322.qmail@daffy.airs.com> (raw)
In-Reply-To: <990910221813.ZM20583@ocotillo.lan>
Date: Fri, 10 Sep 1999 15:18:13 -0700
From: Kevin Buettner <kevinb@cygnus.com>
Why do shared objects on Solaris and Linux have zero-valued
N_FUN stabs?
Good question. It doesn't happen with binutils 2.9.1, but it does
happen in the current development sources.
It's because of this bit of code in elf_i386_relocate_section in
bfd/elf32-i386.c:
/* DWARF will emit R_386_32 relocations in its
sections against symbols defined externally
in shared libraries. We can't do anything
with them here. */
|| (input_section->flags & SEC_DEBUGGING) != 0)))
If I remove that, N_FUN stabs are no longer zero.
Ulrich Drepper checked the patch into the Cygnus sources, before the
sourceware repository was created, with this ChangeLog entry:
1998-12-10 Richard Henderson <rth@cygnus.com>
* elf32-i386.c (elf_i386_relocate_section): Don't fail relocations
in debug sections for symbol defined externally.
Ulrich, Richard, you may recall that I complained about this at the
time. As far as I can recall, and based on my mail logs, we never
resolved that issue. We were left with the above patch, which breaks
things.
At the time I asked for a test case showing the problem, but I never
got one.
My inclination is to simply revert the patch until I find out why it
is needed. Any other suggestions?
Ian
next prev parent reply other threads:[~1999-09-10 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 15:19 Kevin Buettner
1999-09-10 16:51 ` Ian Lance Taylor [this message]
1999-09-11 0:35 ` Richard Henderson
[not found] ` <ian@zembu.com>
1999-09-13 12:45 ` Kevin Buettner
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=19990910234925.15322.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=drepper@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=jimb@cygnus.com \
--cc=kevinb@cygnus.com \
--cc=rth@cygnus.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).