Re: [Libunwind-devel] Function names in C++ program: an interesting behavior by libunwind

[Konstantin Belousov]

On Sat, Apr 17, 2010 at 06:09:00PM -0700, Shravan Gaonkar wrote:
> Hi guys,
>  I modified C program to C++ to test the if libunwind works and
> generates the function names with C++
> 
> 1. When I compile the GtestSimple.cxx on bsd and run it. I dont get
> function names.
> 
> Backtrace across signal handler on alternate stack:
> sighandler: got signal 15, sp=0x2830a4d0 @ 28297e17
>         explicit backtrace:
> 0000000008048a9c                                  (sp=000000002830a3f0)
>         proc=8048a70-8048d04
> 
> 2. If I try to use gdb to find what the problem is, I get the function names.
> 
> 3. After exiting from the gdb, If I still continue to run the program
> I get the function name until I recompile the
> program, after which I am back to state 1.
> 
> Backtrace across signal handler:
> sighandler: got signal 15, sp=0xbfbfe8f0 @ 28297e17
>         explicit backtrace:
> 0000000008048a9c <_Z12do_backtracev+0x2c>         (sp=00000000bfbfe810)
>         proc=8048a70-8048d04
> 
> Any thoughts on such a behavior?
> 
> 
> Shravan
> p.s: I have attached the modified file and the maketest script. You
> can put them in libunwind/tests folder to make your life easy to
> compile
> 
> i am testing on freebsd 7.2 32 bit mode

Does your checkout of libunwind include commit 61f4345a9e812 ?

pgpyLC6nEkgJI.pgp
Description: PGP signature