From: Mark Wielaard <mjw@redhat.com>
To: Jinhua Luo <luajit.io@gmail.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, systemtap@sourceware.org
Subject: Re: [HELP] ubacktrace() problem
Date: Thu, 14 Jan 2016 08:31:00 -0000 [thread overview]
Message-ID: <20160114083126.GB2958@blokker.redhat.com> (raw)
In-Reply-To: <CAAc9rOwnSO2-gFRjD5NaWsUa9vW-ONcABFxXE_Sv6gJOCpnwGg@mail.gmail.com>
On Thu, Jan 14, 2016 at 11:40:19AM +0800, Jinhua Luo wrote:
> Maybe the glibc and its debuginfo on Debian8 is bad?
Unfortunately it is indeed. In theory you won't need debuginfo just for
backtraces if debian could enable -fasynchronous-unwind-tables:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746426
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746516
The other issue is that depending on version debian uses
.zdebug or SHF_COMPRESSED debug sections in their debug
packages. This is partially supported by systemtap (through elfutils)
for some debuginfo, but not for .debug_frame if that is
required for unwinding. This has also been an issue for
other tools like valgrind:
https://bugs.kde.org/show_bug.cgi?id=303877
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810295
Cheers,
Mark
prev parent reply other threads:[~2016-01-14 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 5:47 Jinhua Luo
2016-01-12 14:32 ` Frank Ch. Eigler
2016-01-13 8:19 ` Jinhua Luo
2016-01-13 15:23 ` Frank Ch. Eigler
2016-01-14 3:40 ` Jinhua Luo
2016-01-14 8:31 ` Mark Wielaard [this message]
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=20160114083126.GB2958@blokker.redhat.com \
--to=mjw@redhat.com \
--cc=fche@redhat.com \
--cc=luajit.io@gmail.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).