Summary: | random SIGSEGV on page load | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Julien Etienne <julien.etienne> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, echidnaman |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Julien Etienne
2009-01-21 11:05:49 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :) Unfortunately I am not able to follow the guidelines to get a more detailed report as I am not able to reproduce it systematically nor to get a proper live cd to get more debug information. Another point I would like to point is that I am using the unofficial KDE Live CD provided here: http://home.kde.org/~binner/kde-four-live/ It is very helpful to test the upcoming kde version, but it would be even more useful to you if you provided an official live cd/dvd with all the debug information you need to help testing. Last it would be a good idea to add a button to report the bug directly in the database from the crash handler (with necessary details), rather than having to restart the application and chose "Help>Report Bug". I had another crash with plasma yesterday, but this time with even less information in the stack trace. I hope other reports will be more helpful. Best Regards, Julien @Julien: the debug information is too big to fit in a CD (may be a DVD). This report may be related to bug 165732 Did you do something similar as reported in bug 165732 (and bug 165732 comment 2). If you did, this is a duplicate of that bug Thanks :) *** This bug has been marked as a duplicate of bug 165732 *** |