Application that crashed: kpat Version of the application: 3.2 KDE Version: 4.3.60 (KDE 4.3.60 (KDE 4.4 >= 20090624)) Qt Version: 4.5.2 Operating System: Linux 2.6.31-rc1-00114-g4075ea8 i686 What I was doing when the application crashed: I was able to reproduce this crash, but I am unable to reproduce it at will. It generally arises about halfway through a game, but not always, and it only appears in ~5% of the games played. I have not tried to reproduce it by selecting a particular game number. -- Backtrace: Application: KPatience (kpat), signal: Aborted [Current thread is 0 (LWP 4391)] Thread 2 (Thread 0xf33d9b70 (LWP 4806)): [KCrash Handler] #6 0xf7f15430 in __kernel_vsyscall () #7 0xf6846691 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xf6847dfc in abort () at abort.c:88 #9 0xf688794b in malloc_printerr (action=2, str=0x6 <Address 0x6 out of bounds>, ptr=0x8dca088) at malloc.c:6201 #10 0xf688c116 in __libc_free (mem=0x6) at malloc.c:3677 #11 0x080806db in Solver::solve (this=0x8ddcc08, parent=0x9400d78) at /var/tmp/portage/kde-base/kpat-9999/work/kpat-9999/kpat/patsolve/memory.h:58 #12 0x0808109a in Solver::doit (this=0x8ddcc08) at /var/tmp/portage/kde-base/kpat-9999/work/kpat-9999/kpat/patsolve/patsolve.cpp:639 #13 0x080810ff in Solver::patsolve (this=0x8ddcc08, _max_positions=-1) at /var/tmp/portage/kde-base/kpat-9999/work/kpat-9999/kpat/patsolve/patsolve.cpp:929 #14 0x08060a22 in SolverThread::run (this=0x86cb0a8) at /var/tmp/portage/kde-base/kpat-9999/work/kpat-9999/kpat/dealer.cpp:168 #15 0xf7378daa in QThreadPrivate::start (arg=0x86cb0a8) at thread/qthread_unix.cpp:188 #16 0xf6807696 in start_thread (arg=0xf33d9b70) at pthread_create.c:297 #17 0xf68e89ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xf5f8a710 (LWP 4391)): #0 0xf7f15430 in __kernel_vsyscall () #1 0xf68df1e6 in __poll (fds=0xf696eff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xf5ffeb65 in _xcb_conn_wait (c=0x85b1498, cond=0x85b252c, vector=0xffd6b764, count=0xffd6b768) at xcb_conn.c:306 #3 0xf5fff0ab in _xcb_out_send (c=0x85b1498, vector=0xffd6b764, count=0xffd6b768) at xcb_out.c:338 #4 0xf5fff3ef in xcb_writev (c=0x85b1498, vector=0xffd6b7b8, count=3, requests=117) at xcb_out.c:286 #5 0xf653ba9e in _XSend (dpy=0x85b0c10, data=0x0, size=0) at xcb_io.c:332 #6 0xf653c052 in _XEventsQueued (dpy=0x85b0c10, mode=2) at xcb_io.c:253 #7 0xf6525d8a in XEventsQueued (dpy=0x85b0c10, mode=2) at Pending.c:44 #8 0xf6c4158d in x11EventSourcePrepare (s=0x8582a70, timeout=0xffd6b89c) at kernel/qguieventdispatcher_glib.cpp:79 #9 0xf62e5635 in IA__g_main_context_prepare (context=0x8582de0, priority=0xffd6b91c) at gmain.c:2134 #10 0xf62e5a1d in g_main_context_iterate (context=0x8582de0, block=<value optimized out>, dispatch=1, self=0x8585a88) at gmain.c:2425 #11 0xf62e5f1a in IA__g_main_context_iteration (context=0x8582de0, may_block=1) at gmain.c:2508 #12 0xf74716cd in QEventDispatcherGlib::processEvents (this=0x85a99e8, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327 #13 0xf6c413c0 in QGuiEventDispatcherGlib::processEvents (this=0x85a99e8, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202 #14 0xf744b667 in QEventLoop::processEvents (this=0xffd6bab4, flags=) at kernel/qeventloop.cpp:149 #15 0xf744b834 in QEventLoop::exec (this=0xffd6bab4, flags={i = 0}) at kernel/qeventloop.cpp:197 #16 0xf744d6cd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #17 0xf6bb86ec in QApplication::exec () at kernel/qapplication.cpp:3525 #18 0x08059468 in main (argc=3, argv=0xffd6bed4) at /var/tmp/portage/kde-base/kpat-9999/work/kpat-9999/kpat/main.cpp:267 This bug may be a duplicate of or related to bug 194943 Reported using DrKonqi
Indeed, this looks related to bug 194943. Thanks
this is all buggy glibc if you ask me. *** This bug has been marked as a duplicate of bug 194943 ***