From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: backtrace()...
Date: Mon, 09 Dec 2002 16:37:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805520@msgid-missing> (raw)
>>>>> On 09 Dec 2002 15:33:37 +0100, Fons Rademakers <Fons.Rademakers@cern.ch> said:
Fons> Hi David, I try to use backtrace() (/usr/include/execinfo.h)
Fons> but it returns nothing meaningfull (one 0 stackframe). This is
Fons> on Itanium2:
Fons> Kernel 2.4.18-e.4smp glibc-2.2.4-29.2
Fons> Is this expected or should I do something special?
Yes, the backtrace() in glibc is hopeless. libunwind implements a
working version of backtrace() (see
http://www.hpl.hp.com/research/linux/libunwind/).
--david
reply other threads:[~2002-12-09 16:37 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=marc-linux-ia64-105590709805520@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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