Bug 179900 - KEditFileType (keditfiletype), Signal SIGABRT
Summary: KEditFileType (keditfiletype), Signal SIGABRT
Status: RESOLVED DUPLICATE of bug 178561
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-07 11:29 UTC by Frank Krueger
Modified: 2009-01-07 22:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Krueger 2009-01-07 11:29:11 UTC
Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

Anwendung: KEditFileType (keditfiletype), Signal SIGABRT
 [?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x00007ff778b46645 in raise () from /lib64/libc.so.6
#5  0x00007ff778b47c33 in abort () from /lib64/libc.so.6
#6  0x00007ff77ed0c2d5 in qt_message_output(QtMsgType, char const*) ()
   from /usr/lib64/libQtCore.so.4
#7  0x000000000040d067 in _start ()
Comment 1 Michael Leupold 2009-01-07 12:34:33 UTC
Thanks for your bugreport. Unfortunately the backtrace is not usable because of missing symbols. To create a useful backtrace please install your distribution's debug packages for KDE. Also have a look at: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Please also include information on how the crash happened and if it happens every time you perform the action.
Comment 2 David Faure 2009-01-07 22:45:48 UTC
Must be 159118 or 178561.

*** This bug has been marked as a duplicate of bug 178561 ***