From: Jakub Jelinek <jakub@redhat.com>
To: Steve Munroe <sjmunroe@us.ibm.com>
Cc: Alan Modra <amodra@bigpond.net.au>,
Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix backtrace in statically linked programs on ia64/x86-64/s390{,x}
Date: Tue, 08 Jun 2004 13:53:00 -0000 [thread overview]
Message-ID: <20040608113842.GF5191@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <OF2BC4993C.B7B63197-ON86256EAD.004AAD26-86256EAD.004B4082@us.ibm.com>
On Tue, Jun 08, 2004 at 08:41:54AM -0500, Steve Munroe wrote:
> > libgcc_s.so's unwinder has no way to get at the statically linked binary's
> > unwind tables. For -static, we really want to use _Unwind_* stuff
> > from libgcc_eh.a.
> >
>
> Alan, Is this needed for PPC32/PPC64 as well?
Neither PPC, nor IA-32 use unwind info in backtrace(3).
Until they do, such change is not needed for them.
Jakub
next prev parent reply other threads:[~2004-06-08 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 13:11 Jakub Jelinek
2004-06-08 13:42 ` Steve Munroe
2004-06-08 13:53 ` Jakub Jelinek [this message]
2004-06-11 19:28 ` Roland McGrath
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=20040608113842.GF5191@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=sjmunroe@us.ibm.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).