kdevelop exitting on its own

Aleix Pol aleixpol at kde.org
Mon Oct 20 01:22:57 BST 2014

On Sun, Oct 19, 2014 at 10:27 PM, René J.V. <rjvbertin at gmail.com> wrote:

> On Sunday October 19 2014 20:41:44 Aleix Pol wrote:
> >Does it always happen?
> No, that's the point. When preparing this email it happened twice out of
> three times opening a given session, but not with the other sessions I
> tried to open.
> It's a bit as if there's a gnome inside that takes daemonic pleasure at
> quitting a session that took a long time to open completely.
Maybe you can give it a go with valgrind? I think it's available on OS X.

> >It doesn't seem likely that it's related to the cmake import job,
> >especially considering that this should be happening upon shut down of
> >KDevelop.
> I know it's a far shot, but it's a fact that it never happens before the
> parsing jobs are terminated, nor at a random "long" interval thereafter.
> It's like something sends an exit command to the main thread. In fact, I've
> already managed to set breakpoints in exit() and _exit(), and that told me
> squat. Only that the exit itself was perfectly normal.
Well you can try disabling the plugin and test it again. You can use the
Generic Project Manager for that, for example.

> Are there any timeouts that are applied on processes that go with opening
> a new session?

I'm unsure.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20141020/16d64f3c/attachment.html>

More information about the KDevelop mailing list