Bug 178638 - The application KHangman crashed and caused the signal 6 ( SIGABRT).
Summary: The application KHangman crashed and caused the signal 6 ( SIGABRT).
Status: RESOLVED DUPLICATE of bug 169079
Alias: None
Product: khangman
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Anne-Marie Mahfouf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-24 07:37 UTC by Joseph Boctor
Modified: 2009-01-06 21:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Boctor 2008-12-24 07:37:53 UTC
Version:           I dont know the version (using Devel)
OS:                Linux
Installed from:    Compiled sources

Application: KHangMan (khangman), signal SIGABRT
(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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb60a36c0 (LWP 6328)]
(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]
#5  0xb7fce430 in __kernel_vsyscall ()
#6  0xb6918880 in raise () from /lib/tls/i686/cmov/libc.so.6
#7  0xb691a248 in abort () from /lib/tls/i686/cmov/libc.so.6
#8  0xb752f795 in qt_message_output () from /usr/lib/libQtCore.so.4
#9  0xb752f872 in qFatal () from /usr/lib/libQtCore.so.4
#10 0xb752f8cc in qt_assert_x () from /usr/lib/libQtCore.so.4
#11 0x0805328e in _start ()
#0  0xb7fce430 in __kernel_vsyscall ()
Comment 1 FiNeX 2008-12-24 12:58:59 UTC
Hi! Can you explain how to reproduce the crash?

Moreover, if you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Anne-Marie Mahfouf 2009-01-03 11:04:17 UTC
Hi Joseph, you need to explain how to reproduce the crash. As your backtrace is unseless, the report indicates nothing on the problem and I cannot do anything with it as it is.
Please reproduce the crash and write down how it happens. Also precise how you installed your KDE: the report says from sources, is that from a compiled distribution? is that compiled manually by you? If not, indicate the distribution you are using.
Thanks in advance for following up this report and making us able to deal with the crash!
Comment 3 Anne-Marie Mahfouf 2009-01-06 12:38:13 UTC
Joseph, are you willing to give more precision please before the release?
Comment 4 Anne-Marie Mahfouf 2009-01-06 21:06:08 UTC
Joseph mailed me that he dropped Ubuntu so I am closing this as a duplicate of 169079
Thanks Joseph!

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