On Wed, Feb 22, 2012 at 10:56 PM, Sasikanth <[email protected]> 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 [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
