[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] is backtrace in Signal Handler possible on Linux x

From: POKHARAKAR Sandeep
Subject: Re: [Libunwind-devel] is backtrace in Signal Handler possible on Linux x86_64?
Date: Tue, 23 Aug 2011 06:08:26 +0000

Hello Arun,

> shouldn't be running into any issues on a reasonably new gcc+glibc

My Versions for gcc and glibc are as below. Are these versions ok to get it 
I already have posted my source on this link.

Gcc Version -   gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)

Glibc Version - ldd (GNU libc) 2.5

According to the opinion of few people:
Backtrace is not a async_signal_safe and hence shouldn't be used inside signal 
handler. also, again depends on the compile options of system library routines. 
if those libraries are compiled with -fomit-frame-pointer option then, it is 
not possible the unwind the stack as due to optimization frame pointer is not 
stored on the stack.

How does libunwind library do backtrace internally? Could you please tell me 
the correct version of libunwind for linux x86_64, so that I will try libunwind 
api's for the purpose.

Sandeep Pokharakar
This e-mail communication and any attachments are privileged and confidential 
and intended only for the use of the recipients named above. If you are not the 
intended recipient, please do not review, disclose, disseminate, distribute or 
copy this e-mail and attachments. If you have received this communication in 
error, please notify the sender immediately by email or telephone.

This email and any attachments are intended solely for the use of the 
individual or entity to whom it is addressed and may be confidential and/or 

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email 
and all attachments,

(iii) Dassault Systemes does not accept or assume any liability or 
responsibility for any use of or reliance on this email.

For other languages, go to

reply via email to

[Prev in Thread] Current Thread [Next in Thread]