Re: [Libunwind-devel] Reg: Libunwind with threads lib and system calls

[POKHARAKAR Sandeep]

Hello Arun,

Could you share the concept, How stack has been captured if frame pointers not 
available?
May be any document reference or code snippet?

Regard,
Sandeep


-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Arun Sharma
Sent: Thursday, February 23, 2012 12:46 PM
To: Sasikanth
Cc: address@hidden
Subject: Re: [Libunwind-devel] Reg: Libunwind with threads lib and system calls

On Wed, Feb 22, 2012 at 10:56 PM, Sasikanth <address@hidden> wrote:
> Arun,
>
>   I clearly told stack trace not working because of invalid frame pointer
> ...without a proper frame pointer unwind not able to unwind the stack and
> asked her does  this libunwind supports similar to GDB.

I'm having a hard time parsing this sentence - but if your question
is: can libunwind unwind the stack properly in the absence of frame
pointers using DWARF CFI information, the answer is yes.

Since this is working for you with GDB, I'm guessing that the DWARF
CFI info is there and GDB is able to find it, but libunwind is not. If
you run your program with UNW_DEBUG_LEVEL=xx, we can probably figure
out what's going wrong.

Some linux distributions may strip ELF binaries and ship debug info
separately. It's possible that gdb knows how to find the separately
shipped unwind info, but libunwind doesn't.

> libunwind works only with test programs works not with library.

I know of no such limitation.

I see this is the 7th message on this topic and you're sounding a bit
upset. If you don't provide further information or ask questions in a
form that people can understand, it's going to be hard to help you.

 -Arun

_______________________________________________
Libunwind-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/libunwind-devel
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 http://www.3ds.com/terms/email-disclaimer