https://bugs.kde.org/show_bug.cgi?id=379854
--- Comment #8 from Ian Haber <master.ha...@gmail.com> --- Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault. [Switching to LWP 24069] 0x1fe0af93 in ?? () (gdb) thread apply all bt Thread 16 (LWP 24142): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xb7ffec50 Thread 15 (LWP 24133): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xd13d5c50 Thread 14 (LWP 24132): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xd233dc50 Thread 13 (LWP 24127): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xee6c8d10 Thread 12 (LWP 24121): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xd2ffcbf0 Thread 11 (LWP 24120): #0 0x18472360 in ?? () ---Type <return> to continue, or q <return> to quit--- Backtrace stopped: Cannot access memory at address 0xd37fdb30 Thread 10 (LWP 24119): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xd3ffeb90 Thread 9 (LWP 24118): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xed6c6a10 Thread 8 (LWP 24117): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xf4afec50 Thread 7 (LWP 24116): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xedec7d10 Thread 6 (LWP 24115): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xecec5cb0 Thread 5 (LWP 24078): ---Type <return> to continue, or q <return> to quit--- #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xf73c5c50 Thread 4 (LWP 24077): #0 0x18472709 in ?? () Backtrace stopped: Cannot access memory at address 0x142de0 Thread 3 (LWP 24071): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xbb09ce0 Thread 2 (LWP 24070): #0 0x1f591b5d in ?? () Thread 1 (LWP 24069): #0 0x1fe0af93 in ?? () Backtrace stopped: Cannot access memory at address 0xb2641c20 maybe it is stack corruption? -- You are receiving this mail because: You are watching all bug changes.
