Version: 3.0.0 (using KDE 3.2.0, Gentoo) Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice) OS: Linux (i686) release 2.6.0-gentoo Hi, on much debug output of a program kdevelop 3.0.0 silently dies without a backtrace. to reproduce do the following: create a new project: a kde application framework, compile it, run it, verify that it works. now edit the <project>view.cpp. for example in the method fileNew and add a loop, that only produces debug output: void crashtestdummy::fileNew() { // this slot is called whenever the File->New menu is selected, // the New shortcut is pressed (usually CTRL+N) or the New toolbar // button is clicked while ( true ) { qDebug( "this is a debug statement..." ); qDebug( "this is a very looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong debug statement..." ); } // create a new window (new crashtestdummy)->show(); } now run the program. for me it runs about 3 seconds and then the kdevelop window disappears. then i have to kill the test app. also sometimes it seems as some debug lines in the kdevelop application window are printed more than once... i hope this is enough description to reproduce. thanks, Holger
I'm not surprised.. it's busted in many interesting ways. Still trying to find a good and not too unfeatured solution.
ProcessWidget::maybeScrollToBottom() uses processEvents which is very suspicious and is likely to cause unwanted recursion in this case.
Not anymore, so maybe it won't crash now. Hmm.. forgot to backport it, I think..
I just realized, this is very probably a dupe. *** This bug has been marked as a duplicate of 67217 ***