[Top][All Lists]

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

[Libunwind-devel] is backtrace in Signal Handler possible on Linux x86_6

From: POKHARAKAR Sandeep
Subject: [Libunwind-devel] is backtrace in Signal Handler possible on Linux x86_64?
Date: Mon, 22 Aug 2011 07:23:56 +0000

Hello All,


Which is the latest stable version of libunwind available for Linux x86_64?


I had used this a year back to capture callstack of self thread. But now my requirement is slightly different.


In my project, I am having my own Signal handler for a particular Signal SIGUSR1. This Signal is being raised for each thread in the application periodically. so, the Signal handler is executed for each thread repeatedly after specific time interval.


Now, I want to call backtrace in the Signal Handler, it doesn’t work sometimes. Specifically, when there are calls like malloc/free (from standard linux library) on the callstack. I observed crash in backtrace.  (e.g.     backtrace()

<- SignalHandler()

<- malloc()

<- methodA()

<- threadA()

<- main())


I am thinking now to use libunwind library API() instead of backtrace() here. will it be supporting? Are there any specific compiler option settings to make this working?  


Please give me some hints on the problem.    




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 privileged.

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]