Could you confirm that you're not running configure with
Yes, i built libunwind with
option only. Should i have "--enable-cxx-exceptions" also?
Also does libunwind dependent on any other libraries (i.e.) is it dependent on a debug version of a library? like ld (in Valgrind) or libc? Coz all the libraries running in target are stripped production versions without debug.
Should i include libunwind first in LD_LIBRARY_PATH? Right now it's at the end? If libunwind takes over gcc libs, is the order of symbol search in LD_LIBRARY_PATH matters?
I recompiled libunwind with "--enable-cxx-exceptions" and it did not change the behavior.
I compile out the contents of "mybacktrace" contents (posted earlier) and just returned entries = 0; With this, even when i link with -libunwind it is stable and yes no stack trace.
Then instead of compiling out, i tried a runtime version like this
... <unwind stack as posted earlier>
and needBacktrace is initialized to zero
With this it crashes like before even though my library is not calling any of the libunwind apis.
When i find the diff between these two versions, only the following symbols are added extra
Just by having these symbols in library is causing crash even though we are not calling it. Any thoughts?