From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.cygnus.com
Subject: [PATCH] Fix segfault relocating debugging sections on powerpc-*-linux-gnu
Date: Thu, 29 Jul 1999 16:52:00 -0000 [thread overview]
Message-ID: <19990729195420.A20264@them.org> (raw)
When the attached testcase is compiled on powerpc-linux with 'c++ -fPIC
-shared -g segvtest.cc' it causes a SEGV in the linker. Franz Sirl
noticed that elf32-i386.c specifically avoids relocations in sections
with SEC_DEBUGGING set; this patch adds the same to elf32-ppc.c. It
also copies the warning from elf32-i386.c in the same situation; the if
condition here (here being elf32-ppc.c:3000 or so) does not obviously
guarantee that output_section will not be NULL, and there could be
other cases it misses. I see no reason to have ld segfault
mysteriously :)
I would have added a testcase, but the organization of ld/testsuite/
eludes me.
[Please CC: me in any list replies, I'm not on this list]
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
reply other threads:[~1999-07-29 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990729195420.A20264@them.org \
--to=drow@false.org \
--cc=binutils@sourceware.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).