Summary: | cannot generate core files for crashing applications | ||
---|---|---|---|
Product: | [Applications] drkonqi | Reporter: | SuD <sudako> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED REMIND | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
SuD
2003-08-27 22:09:06 UTC
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. |