Bug 231051 - KPatience demo segfault cheating
Summary: KPatience demo segfault cheating
Status: RESOLVED DUPLICATE of bug 204073
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 02:12 UTC by emeraldsage
Modified: 2010-03-17 02:23 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 emeraldsage 2010-03-17 02:12:42 UTC
Application that crashed: kpat
Version of the application: 3.2
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-2.slh.4-sidux-amd64 x86_64

What I was doing when the application crashed:
played klondike, switched the game mode to 3-draw and proceeded to lose. The game said I could win, I watched the demo play illegal moves (like kings on 8s) until it segfaulted.

 -- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x00000000004288b8 in DealerScene::demo (this=0x2963db0) at /tmp/buildd/kdegames-4.3.4/kpat/dealer.cpp:1694
#6  0x000000000042bc38 in DealerScene::qt_metacall (this=0x2963db0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff45a2ea10)
    at /tmp/buildd/kdegames-4.3.4/obj-x86_64-linux-gnu/kpat/dealer.moc:155
#7  0x00000000004418b5 in Klondike::qt_metacall (this=0x7fff45a2e8c0, _c=QMetaObject::InvokeMetaMethod, _id=55273520, _a=0x4) at /tmp/buildd/kdegames-4.3.4/obj-x86_64-linux-gnu/kpat/klondike.moc:62
#8  0x00007fd4d9d68df2 in QMetaObject::activate (sender=0x2e42d30, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x4) at kernel/qobject.cpp:3112
#9  0x00007fd4d9d63353 in QObject::event (this=0x2e42d30, e=0x0) at kernel/qobject.cpp:1074
#10 0x00007fd4d8c6501d in QApplicationPrivate::notify_helper (this=0x26d3360, receiver=0x2e42d30, e=0x7fff45a2f0c0) at kernel/qapplication.cpp:4065
#11 0x00007fd4d8c6d07a in QApplication::notify (this=0x7fff45a2f530, receiver=0x2e42d30, e=0x7fff45a2f0c0) at kernel/qapplication.cpp:4030
#12 0x00007fd4dabc7de6 in KApplication::notify (this=0x7fff45a2f530, receiver=0x2e42d30, event=0x7fff45a2f0c0) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007fd4d9d53c9c in QCoreApplication::notifyInternal (this=0x7fff45a2f530, receiver=0x2e42d30, event=0x7fff45a2f0c0) at kernel/qcoreapplication.cpp:610
#14 0x00007fd4d9d802c6 in QCoreApplication::sendEvent (this=0x26d8b60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#15 QTimerInfoList::activateTimers (this=0x26d8b60) at kernel/qeventdispatcher_unix.cpp:580
#16 0x00007fd4d9d7c658 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#18 0x00007fd4d4c7b90e in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007fd4d4c7f2c8 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007fd4d4c7f3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x00007fd4d9d7c39c in QEventDispatcherGlib::processEvents (this=0x26a0160, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#22 0x00007fd4d8cfbf1f in QGuiEventDispatcherGlib::processEvents (this=0x7fff45a2e8c0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007fd4d9d52562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007fd4d9d52934 in QEventLoop::exec (this=0x7fff45a2f370, flags=...) at kernel/qeventloop.cpp:201
#25 0x00007fd4d9d54ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000416584 in main (argc=<value optimized out>, argv=<value optimized out>) at /tmp/buildd/kdegames-4.3.4/kpat/main.cpp:267

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

Reported using DrKonqi
Comment 1 Parker Coates 2010-03-17 02:23:54 UTC
Thanks for the report, but this bug has already been reported and fixed in SC4.4.

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