Bug 217505 - kdiamond after closing segfaulted
Summary: kdiamond after closing segfaulted
Status: RESOLVED DUPLICATE of bug 202810
Alias: None
Product: kdiamond
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Majewsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-05 23:16 UTC by xtrix
Modified: 2009-12-05 23:19 UTC (History)
2 users (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 xtrix 2009-12-05 23:16:39 UTC
Application that crashed: kdiamond
Version of the application: 1.2
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.6-145.fc12.i686 i686

What I was doing when the application crashed:
I wanted to close (exit) KDiamond normally - when kdiamond's window disappeared the crash reporting asistant have been displayed with segfault info. ;-) 

 -- Backtrace:
Application: KDiamond (kdiamond), signal: Segmentation fault
[KCrash Handler]
#6  0x0805716a in KDiamond::GameState::state (this=0x85e2920) at /usr/src/debug/kdegames-4.3.3/kdiamond/src/game-state.cpp:80
#7  0x0805507b in Board::timerEvent (this=<value optimized out>, event=<value optimized out>) at /usr/src/debug/kdegames-4.3.3/kdiamond/src/board.cpp:312
#8  0x021dcd3f in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1074
#9  0x0442be15 in QGraphicsScene::event (this=<value optimized out>, event=<value optimized out>) at graphicsview/qgraphicsscene.cpp:3904
#10 0x03df0b24 in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:4065
#11 0x03df8281 in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3605
#12 0x0048602b in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#13 0x021ccd73 in QCoreApplication::notifyInternal (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at kernel/qcoreapplication.cpp:610
#14 0x021fa2be in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#15 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:580
#16 0x021f7c21 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#17 0x060b0118 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#18 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#19 0x060b3a48 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#20 0x060b3b74 in IA__g_main_context_iteration (context=0x84adc90, may_block=<value optimized out>) at gmain.c:2654
#21 0x021f7b6d in QEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x03e90356 in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x021cb2aa in QEventLoop::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:149
#24 0x021cb70a in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:201
#25 0x021cdbf7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x03df09a8 in QApplication::exec () at kernel/qapplication.cpp:3525
#27 0x08059ae0 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdegames-4.3.3/kdiamond/src/main.cpp:87

This bug may be a duplicate of or related to bug 202810

Reported using DrKonqi
Comment 1 FiNeX 2009-12-05 23:19:46 UTC

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