Piotr Mierzwinski <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #2 from Piotr Mierzwinski <> ---
Sorry. This was what produced by DrKonqi when I wanted close working in
background KDevelop process. Before KDevelop only closed itself. I wasn't be
able to run it again, because in background I had working KDevelop. I killed
this process and this triggered DrKonqi.

Today I tried to reproduce crash running KDevelop in dbg, but again KDevelop
just closed its main window. I had to send couple times signal "CONT" (from
System activity tool - invoked by Ctrl+Esc), to get prompt of dbg. After that I
run command "cont" and again no prompt and nothing happened. I repeat this
couple of time. Finally I run "kill -CONT kdevelop_pid" from konsole and after
"cont" command in dbg  returned: "Thread 1 "kdevelop" received signal SIGSEGV,
Segmentation fault.". In backtrace I noticed that this is again crash in

#8  0x00007ffff7a8701b in KDevelop::MainWindow::~MainWindow()
(this=this@entry=0x8e4f50, __in_chrg=<optimized out>, __vtt_parm=<optimized

I attach dbg output.

You are receiving this mail because:
You are watching all bug changes.

Reply via email to