From: Kevin Buettner <kevinb@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: SOFUN_ADDRESS_MAYBE_MISSING
Date: Mon, 06 Oct 2003 16:44:00 -0000 [thread overview]
Message-ID: <1031006164419.ZM11491@localhost.localdomain> (raw)
In-Reply-To: Mark Kettenis <kettenis@chello.nl> "SOFUN_ADDRESS_MAYBE_MISSING" (Oct 6, 2:42pm)
On Oct 6, 2:42pm, Mark Kettenis wrote:
> I'm wondering what to do with SOFUN_ADDRESS_MAYBE_MISSING. It started
> out (and still largely is) a hack to work around a problem with
> stabs-in-ELF with Sun's C compiler. Later it also got enabled on some
> Linux variants, to work around a bug in HJ's Linux binutils IIRC.
>
> The safest thing to do is probably to turn this into a multi-arch
> variable, and set that variable for all targets that #define
> SOFUN_ADDRESS_MAYBE_MISSING. I winder however, what the impact would
> be of enabling this on all ELF targets, since that would make it
> easier to debug object modules created with the Sun compiler to
> FreeBSD/sparc64 for example.
It's been a while since I've studied this problem, but the last time
I looked at it, enabling SOFUN_ADDRESS_MAYBE_MISSING for all targets
looked pretty safe to me.
Kevin
next prev parent reply other threads:[~2003-10-06 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 12:42 SOFUN_ADDRESS_MAYBE_MISSING Mark Kettenis
2003-10-06 16:44 ` Kevin Buettner [this message]
2003-10-07 16:44 ` SOFUN_ADDRESS_MAYBE_MISSING Jim Blandy
2003-10-07 4:24 ` SOFUN_ADDRESS_MAYBE_MISSING Jim Blandy
2003-10-15 18:21 ` SOFUN_ADDRESS_MAYBE_MISSING Elena Zannoni
2003-10-16 19:49 ` SOFUN_ADDRESS_MAYBE_MISSING Mark Kettenis
2003-10-15 18:44 SOFUN_ADDRESS_MAYBE_MISSING Michael Elizabeth Chastain
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=1031006164419.ZM11491@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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