https://bugs.kde.org/show_bug.cgi?id=466229
--- Comment #3 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Stephan Kulow from comment #2) > Hi, can you export KDE_DEBUG=1 before starting it from console? Then > something useful should appear in coredumpctl (typing from memory as I'm not > having a computer around). Kernel CONFIG_COREDUMP=n, so coredumpctl never gets the cores from the kernel. I could change that if necessary (tho would rather not deal with figuring out all that config), but what about running via gdb instead? Meanwhile , dmesg does say SolverThread .... SIGSEGV ... error 6 in kpat ... Currently the gdb likely isn't much help due to stripped binaries, but here's what I get ATM... A bunch of New Thread ... Thread exited pairs, apparently one per move, I guess for the solver threads. Then at the SIGSEGV... [New Thread 0x7fffd99fc6c0 (LWP 13533)] Thread 381 "SolverThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd99fc6c0 (LWP 13533)] 0x00005555555d762e in ?? () (gdb) bt #0 0x00005555555d762e in ?? () #1 0x00005555555d8546 in ?? () #2 0x00005555555d9726 in ?? () #3 0x00005555555da057 in ?? () #4 0x000055555558eab7 in ?? () #5 0x00007ffff64cb05f in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x00007ffff5ee042d in ?? () from /usr/lib64/libc.so.6 #7 0x00007ffff5f5943c in ?? () from /usr/lib64/libc.so.6 (gdb) I'll have to look up again how to build unstripped, with debugging enabled (IIRC gentoo/kde has a guide I'll need to reread, I've done it once before for something and it wasn't difficult) to fill in the ??s. Hopefully this weekend... -- You are receiving this mail because: You are watching all bug changes.
