2013/8/16 Timothy Pearson <kb9vqf@pearsoncomputing.net>
The new routine prints a stack trace that is very close to gdb's output,
information which then makes debugging very difficult.
Either way, you are correct--the code section in question is only
activated when debugging is turned on at compile time (#undef NDEBUG in
tdeioslavebase.cpp). Furthermore, the output is logged to
~./xsession-errors as text, not via a popup kcrash dialog.
Tim
ok... I suppose it would be nice to make it an another backend for kdBacktrace. but before starting to I've got couple more questions:
Does it have some special requirements? e.g. debug information (splitted or not) or source code installed?
Is there any library that implements it and provides higher-level API?