Version: (using KDE KDE 3.1) Installed from: Debian testing/unstable Packages OS: Linux When kvirc (or any other kde application) crashes it does not generate a core, even though that i previously set "ulimit -c unlimited" on the same shell. Later, when DrKonqui dialog appears it shows a useless backtrace (related to KCrash function, but not kvirc's offending function). The thing is that it would be a nice idea (if technically possible) to have a button in DrKonqui for saving core files (Save core as...). This would help debugging much. Else i would have to run kvirc from gdb, but that is uncomfortable.
export KDE_DEBUG=1
aieee, sorry, something is b0rken.
I had the exact same problem as the original reporter. So I investigated into the KCrash and drkonqi source code and I noticed that there is an obscure configuration option. Add the following section to .kde/share/config/kdeglobals: [drkonqi] ConfigName=developer This changes the "skin" of drkonqi to a (for developers) more useful one. It especially allows you to open a Konsole window with gdb attached to the process. So the *real* problem here is that one has to dive into the code of drkonqui to find this *highly* useful feature. I just checked again, and neither the FAQ nor the easily accessible debugging howtos mentions this feature.
Added the option to http://techbase.kde.org/index.php?title=Development/FAQs/Debugging_FAQ . Does the actual problem still exist?
Waiting for a response.