https://bugs.kde.org/show_bug.cgi?id=312692
--- Comment #8 from Fernando Vilas <fvi...@iname.com> --- Sorry about the delayed response... When you ran the test in gdb, after it crashed, the command "where" should have given you a stack trace. To try to get a better trace, you could try "break filename:line_number" and then use "step" to get into a function and "next" to execute the line but not step in. I will say that a GUI debugger tends to help this process. The other option is using qDebug() to get a ton of information. There is already a DBG macro that is commented out, but could be changed to actually provide output. From there, you could add additional debugging statements. I have used both GUI debuggers and the print-statement method, and which is the right answer depends on the problem at hand and the mood of the developer at the time. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
