Bug 369393 - Floating point exception at startup
Summary: Floating point exception at startup
Status: RESOLVED FIXED
Alias: None
Product: knights
Classification: Applications
Component: general (show other bugs)
Version: 2.5.0
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Miha Čančula
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-09-26 20:01 UTC by Thure Dührsen
Modified: 2017-09-09 16:25 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thure Dührsen 2016-09-26 20:01:16 UTC
Application: knights (2.5.0)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-686-pae i686
Distribution: Debian GNU/Linux 8.5 (jessie)

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

I tried to set up a match between two engines. Upon confirmation, the program crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Knights (knights), signal: Floating point exception
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[KCrash Handler]
#7  0x0806aa82 in Knights::UciProtocol::requestNextMove (this=0x9a66660) at /build/knights-woT5wK/knights-2.5.0/src/proto/uciprotocol.cpp:185
#8  0x08089470 in Knights::Manager::sendPendingMove (this=0x9809ae8) at /build/knights-woT5wK/knights-2.5.0/src/gamemanager.cpp:695
#9  0x0805c908 in Knights::Manager::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /build/knights-woT5wK/knights-2.5.0/obj-i486-linux-gnu/src/moc_gamemanager.cpp:115
#10 0xb58fd7a2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#11 0xb59073c0 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#12 0xb5901ffe in QObject::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#13 0xb5ef750a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#14 0xb5efe420 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#15 0xb746ccdc in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#16 0xb58e742a in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#17 0xb591c1ce in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#18 0xb5918e8c in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#19 0xb1e4bdb4 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#20 0xb1e4c0d9 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0xb1e4c1a6 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#22 0xb5919839 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#23 0xb5fab516 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#24 0xb58e5d9f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#25 0xb58e612e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#26 0xb58ec2b6 in QCoreApplication::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#27 0xb5ef5614 in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#28 0x0805ad46 in main (argc=5, argv=0xbfacf864) at /build/knights-woT5wK/knights-2.5.0/src/main.cpp:79

Reported using DrKonqi
Comment 1 Burkhard Lück 2016-09-27 06:02:34 UTC
With

1) Ubuntu 16.04.1 LTS
$ knights --version
Qt: 4.8.7
KDE: 4.14.16
Knights: 2.5.0

2) Compiled from sources
Qt: 4.8.2
KDE Development Platform: 4.14.18
Knights: 2.5.0

3) Compiled from sources
Qt: 4.8.2
KDE Frameworks 5.27.0
Qt 5.6.1 (built against 5.6.1)

not reproducible for me

Which chess engines do you use? are they installed?
Comment 2 Alexander Semke 2017-09-09 16:25:48 UTC
The Qt4 version is not maintained anymore. The KF5 based code of Knights doesn't have this error. Please give it a try.

I'm closing the ticket.