Bug 290246 - Knights crashed
Summary: Knights crashed
Status: RESOLVED WORKSFORME
Alias: None
Product: knights
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.3.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Miha Čančula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-31 11:16 UTC by Germano Massullo (Thetra)
Modified: 2018-01-09 16:45 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Germano Massullo (Thetra) 2011-12-31 11:16:00 UTC
Application: knights (2.3.2)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.8.0
Operating System: Linux 3.1.6-1.fc16.i686 i686
Distribution: "Fedora release 16 (Verne)"

-- Information about the crash:
- What I was doing when the application crashed:

I was playing knights when the application suddendly crashed. The crash, I think, maybe triggered by a move

The crash can be reproduced some of the time.

-- Backtrace:
Application: Knights (knights), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#7  0x080640e4 in Knights::Piece::pieceType (this=0x0) at /usr/src/debug/knights-2.3.2/src/core/piece.cpp:169
#8  0x0807eb6c in Knights::ChessRules::moveMade (this=0x8bd5438, m=...) at /usr/src/debug/knights-2.3.2/src/rules/chessrules.cpp:556
#9  0x0805cde3 in sendPendingMove (this=0x8a7d110) at /usr/src/debug/knights-2.3.2/src/gamemanager.cpp:589
#10 Knights::Manager::sendPendingMove (this=0x8a7d110) at /usr/src/debug/knights-2.3.2/src/gamemanager.cpp:582
#11 0x0805abfd in Knights::Manager::qt_metacall (this=0x8a7d110, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbf8c3e10) at /usr/src/debug/knights-2.3.2/src/moc_gamemanager.cpp:115
#12 0x4613a29e in metacall (argv=0xbf8c3e10, idx=12, cl=QMetaObject::InvokeMetaMethod, object=0x8a7d110) at kernel/qmetaobject.cpp:245
#13 QMetaObject::metacall (object=0x8a7d110, cl=QMetaObject::InvokeMetaMethod, idx=12, argv=0xbf8c3e10) at kernel/qmetaobject.cpp:240
#14 0x46148d8d in QMetaObject::activate (sender=0x8e3b8a8, m=0x4628c398, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3565
#15 0x46152be6 in QSingleShotTimer::timeout (this=0x8e3b8a8) at .moc/release-shared/qtimer.moc:97
#16 0x46152ccd in QSingleShotTimer::timerEvent (this=0x8e3b8a8) at kernel/qtimer.cpp:317
#17 0x4614de44 in QObject::event (this=0x8e3b8a8, e=0xbf8c431c) at kernel/qobject.cpp:1156
#18 0x466c9a34 in notify_helper (e=0xbf8c431c, receiver=0x8e3b8a8, this=0x89239a8) at kernel/qapplication.cpp:4518
#19 QApplicationPrivate::notify_helper (this=0x89239a8, receiver=0x8e3b8a8, e=0xbf8c431c) at kernel/qapplication.cpp:4490
#20 0x466ceed3 in QApplication::notify (this=0xbf8c431c, receiver=0x8e3b8a8, e=0xbf8c431c) at kernel/qapplication.cpp:4247
#21 0x472c1972 in KApplication::notify (this=0xbf8c463c, receiver=0x8e3b8a8, event=0xbf8c431c) at /usr/src/debug/kdelibs-4.7.4/kdeui/kernel/kapplication.cpp:311
#22 0x461331de in QCoreApplication::notifyInternal (this=0xbf8c463c, receiver=0x8e3b8a8, event=0xbf8c431c) at kernel/qcoreapplication.cpp:876
#23 0x46167f90 in sendEvent (event=0xbf8c431c, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#24 QTimerInfoList::activateTimers (this=0x8928884) at kernel/qeventdispatcher_unix.cpp:611
#25 0x46165659 in timerSourceDispatch (source=0x8928850) at kernel/qeventdispatcher_glib.cpp:186
#26 timerSourceDispatch (source=0x8928850) at kernel/qeventdispatcher_glib.cpp:180
#27 0x419675bf in g_main_dispatch (context=0x89268f0) at gmain.c:2425
#28 g_main_context_dispatch (context=0x89268f0) at gmain.c:2995
#29 0x41967d00 in g_main_context_iterate (context=0x89268f0, block=1100441504, dispatch=1, self=0x8928820) at gmain.c:3073
#30 0x41967faf in g_main_context_iteration (context=0x89268f0, may_block=1) at gmain.c:3136
#31 0x46165e88 in QEventDispatcherGlib::processEvents (this=0x88fdd40, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#32 0x4677e28b in QGuiEventDispatcherGlib::processEvents (this=0x88fdd40, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#33 0x461320ce in QEventLoop::processEvents (this=0xbf8c4594, flags=...) at kernel/qeventloop.cpp:149
#34 0x46132379 in QEventLoop::exec (this=0xbf8c4594, flags=...) at kernel/qeventloop.cpp:204
#35 0x4613751b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#36 0x466c7835 in QApplication::exec () at kernel/qapplication.cpp:3779
#37 0x08058968 in main (argc=5, argv=0xbf8c47a4) at /usr/src/debug/knights-2.3.2/src/main.cpp:87

Reported using DrKonqi
Comment 1 Miha Čančula 2012-01-14 14:31:27 UTC
Yes, from the backtrace it looks to be triggered by a move, and it crashes only after making it. 

Was the move by any chance castling? I know I made some fixes to that since 2.3.2, so it may be it. Anyhow, I have tested the 2.4 branch more extensively and I didn't get any random crashes, could you update to a newer version?
Comment 2 Miha Čančula 2012-01-19 16:19:40 UTC
- Did it happen with castling or with all moves?
- Does it happen with 2.4.1 as well?
Comment 3 Germano Massullo (Thetra) 2012-01-27 16:39:59 UTC
I am not able to reproduce the crash.
Actually I am on 2.4.0 and I still have not had the problem