From: Geoff Keating <geoffk@geoffk.org>
To: howarth@nitro.med.uc.edu
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: binutils patch
Date: Mon, 08 Oct 2001 01:03:00 -0000 [thread overview]
Message-ID: <200110080821.BAA09479@geoffk.org> (raw)
In-Reply-To: <200110071300.JAA15309@nitro.msbb.uc.edu>
> Date: Sun, 7 Oct 2001 09:00:19 -0400 (EDT)
> From: Jack Howarth <howarth@nitro.med.uc.edu>
> This is similar to my sparc32 patch from July.
> Basically, I don't think we should output .rela.* sections for debugging
> sections in shared libraries (of course, unless --emit-relocs), gdb doesn't
> use it anyway and most other ELF backends don't emit them.
I believe this is a known problem with GDB which will be corrected
eventually. With stabs, it's not clear what the correct behaviour is,
but with DWARF (which will be the default in GCC 3.1) it's clearly
correct to generate and use the relocs.
--
- Geoffrey Keating <geoffk@geoffk.org>
next parent reply other threads:[~2001-10-08 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200110071300.JAA15309@nitro.msbb.uc.edu>
2001-10-08 1:03 ` Geoff Keating [this message]
2001-10-08 1:22 ` Jakub Jelinek
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=200110080821.BAA09479@geoffk.org \
--to=geoffk@geoffk.org \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=howarth@nitro.med.uc.edu \
/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