kdevelop exitting on its own

Milian Wolff mail at milianw.de
Mon Oct 20 12:59:25 BST 2014

On Monday 20 October 2014 13:48:05 René J.V. Bertin wrote:
> On 20 October 2014 10:46, Milian Wolff <mail at milianw.de> wrote:
> >> 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.

Hey Rene,

please keep the discussion on-list.

> It's not a crash or abort; DrKonqi now actually works better on OS X
> than on Linux (at least as far as actual submission goes; it has been
> adapted to the new bugzilla protocol). But even before it would
> attempt to start, and failing that OS X has its own crash reporter.
> None of these show up, and when I run from the debugger KDevelop exits
> normally. Besides, when it happened on Linux DrKonqi also didn't
> start.
> That's what I've been trying to describe: the exit proceeds normally,
> it is just triggered for unknown and unpredictable reasons.

OK, odd. Then set a breakpoint in exit() or QApplication::quit or similar and 
figure out where its being called from.


Milian Wolff
mail at milianw.de

More information about the KDevelop mailing list