03-20-2013 10:15 AM
Does anyone know how to get more than three backtrace frames in the debug window of momentics? Each of my threads shows only the innermost three stack frames. Very frustrating. I had a look through the settings but couldn't find anything. 'show backtrace limit' on the gdb claims the backtrace is unlimited.
03-20-2013 10:27 AM
bt #0 0x02021b14 in MsgReceivePulse_r () from C:\\bbndk\\target_10_0_9_1673\\qnx6\\armle-v7\\usr\\lib/ldqnx.so.2 #1 0x781c841a in ?? () #2 0x781c841a in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Looks like the problem is a corrupt stack. Are others experiencing this, or have I done something special? My application by and large works reliably, but I was trying to get at a specific bug which occurs rarely. Yet, despite it working fine, I always have this limitation with the stack frames.
03-21-2013 11:18 PM
I get the corrupt stack message on any thread that was created/handled by one of the BB/QNX libs. I don't think I would be worried in that case. (It could have been because the way the library was built -- omit frame pointers, no debug info, etc). All my other threads I can see every frame no problem. I'm running with -O0 (no inlining) and -g.
[Switching to thread 10 (pid 102297834 tid 10)]
#0 0x017c1b14 in MsgReceivePulse () from G:\\bbndk\\target_10_0_10_672\\qnx6\\armle-v7\\usr
bt
#0 0x017c1b14 in MsgReceivePulse () from G:\\bbndk\\target_10_0_10_672\\qnx6\\armle-v7\\usr
#1 0x7851841a in ?? () from G:\\bbndk\\target_10_0_10_672\\qnx6\\armle-v7\\usr
#2 0x7851841a in ?? () from G:\\bbndk\\target_10_0_10_672\\qnx6\\armle-v7\\usr
Backtrace stopped: previous frame identical to this frame (corrupt stack?)