Take the 2-minute tour ×

Currently, Apportable doesn't show any stack trace on crash by C/C++ exception.

How can I make it to print stack-trace when it is crashed?

share|improve this question

1 Answer 1

up vote 0 down vote accepted

You can use apportable debug to attach a gdb debugger to the app. Then use the command continue to get to the crash; backtrace to see the trace; up, down, and frame {number} to navigate through the trace; and print {expression} to examine state.

More information in the docs page.

For C++ exceptions in particular, you will get a confusing stack trace. We'll investigate adding better debugger support for these. In the meantime you could set a breakpoint on the throw(break __cxa_throw).

share|improve this answer
I also wish to have a way to set a breakpoint with apportable debug command line. –  Eonil Jul 20 '13 at 0:09
You can add breakpoints (or any gdb commands) to a $HOME/.gdbinit file. Also gdb command line history (with up arrow) is configured into the apportable gdb setup –  Paul Beusterien Jul 20 '13 at 2:42

Your Answer


