This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [HELP] ubacktrace() problem
- From: Mark Wielaard <mjw at redhat dot com>
- To: Jinhua Luo <luajit dot io at gmail dot com>
- Cc: "Frank Ch. Eigler" <fche at redhat dot com>, systemtap at sourceware dot org
- Date: Thu, 14 Jan 2016 09:31:26 +0100
- Subject: Re: [HELP] ubacktrace() problem
- Authentication-results: sourceware.org; auth=none
- References: <CAAc9rOzFmkSKJCmi=0=Vggvaf3-VnwgfHFPfBxG475NKso3arQ at mail dot gmail dot com> <y0m7fje98cy dot fsf at fche dot csb> <CAAc9rOxJNeVvyjeRX==GpNU9H=Sh+AfFUgLtLPqxFpWJnj_K3w at mail dot gmail dot com> <20160113152312 dot GC7497 at redhat dot com> <CAAc9rOwnSO2-gFRjD5NaWsUa9vW-ONcABFxXE_Sv6gJOCpnwGg at mail dot gmail dot 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