[Kde-bindings] debugging a korundum program after a crash

[Stefano Crocco]

My korundum4 program is randomly crashing. By 'crashing', I don't mean it's 
raising an exception which isn't caught, but that it's crashing at the C++ 
level. This could mean I just found a bug in qtruby or korundum but it's much 
more likely that it simply means my program is doing something it shouldn't. 

If my program raised an exception, I could simply look at the line where the 
exception was raised and from there follow the program flow and try to 
understand what's wrong. Of course, with a C++-level crash, I can't do that, 
since the backtrace only contains calls to qt/kde/smoke/qtruby/ruby internal 
functions.

Do you have any advice on how to proceed?

Thanks in advance

Stefano