kdevelop exitting on its own

Milian Wolff mail at milianw.de
Mon Oct 20 09:46:40 BST 2014

On Sunday 19 October 2014 00:36:58 René J.V. Bertin wrote:
> On both my Linux and my OS X systems I've noticed that KDevelop 4.7.0 and
> 4.7.60 have an irregular habit of exitting after completing the
> parse-on-open of the projects in the session I started with. This happens
> regardless of whether I'm doing something in KDevelop or elsewhere. It's
> been suggested to set a breakpoint in KDevelop::MainWindow::~MainWindow but
> hasn't yet proved productive (rather the contrary; starting kdevelop under
> a debugger take a lot of patience on the systems I have at my disposal).
> So I added a qDebug output of kBackTrace() in
> KDevelop::MainWindow::~MainWindow, assuming I'd be able to get some idea of
> where the exit request came from when it happens.
> Turns out KDevelop exits without calling this MainWindow destructor:

This is then most likely a crash. Since DrKonqi (afaik) is not yet available 
on Mac, you won't get notified about the crash. Run the thing through a 
debugger and figure out whats going on. Valgrind, as Aleix noted, would also 
be a good idea.

Milian Wolff
mail at milianw.de

More information about the KDevelop mailing list