Stack trace after signal 11
19 views
Skip to first unread message
Joshua Peterson
Sep 8, 2009, 2:24:43 PM9/8/09
to zerobugs
I'm using the CentOS 5.2 x86_64 version of ZeroBugs (Debugger Engine
BETA (Nov 27 2008) 1.16.126) on RHEL 5.3. When I receive a signal 11
in my application, I only see one method in the stack trace window,
the method where the signal 11 occurred (call it foo()). I don't see
any of the other methods that called foo() in the stack trace window.
Is this the expected behavior, or do I need to enable some option in
the debugger? Note that with gdb, I can do a bt and see the full
stack trace. I'm compiling with gcc 3.4.6. Thanks.
Josh
BETA (Nov 27 2008) 1.16.126) on RHEL 5.3. When I receive a signal 11
in my application, I only see one method in the stack trace window,
the method where the signal 11 occurred (call it foo()). I don't see
any of the other methods that called foo() in the stack trace window.
Is this the expected behavior, or do I need to enable some option in
the debugger? Note that with gdb, I can do a bt and see the full
stack trace. I'm compiling with gcc 3.4.6. Thanks.
Josh
Reply all
Reply to author
Forward
0 new messages