kdevelop exitting on its own

Aleix Pol aleixpol at kde.org
Fri Nov 7 00:53:22 GMT 2014


On Thu, Nov 6, 2014 at 10:07 AM, René J.V. <rjvbertin at gmail.com> wrote:

> On Thursday November 06 2014 03:52:25 Aleix Pol wrote:
>
> >What you should be looking for is what is making the event loop end. You
> >already see that the event loop ends because the application shuts down...
>
> Indeed, I can just see that someone/something decided it was time to shut
> down. Sadly we're talking about Qt's main event loop which isn't easy to
> debug.
> Any suggestions on how to do specific event debugging are welcome!
>
> Yesterday I had another case where KDevelop exited moments after I hit the
> Stop All button to terminate a bunch of parsing jobs, another one while I
> was about to commit or push some changes, and at least one was on Linux.
>
I haven't seen this really. I'm sorry.


>
> Something I've been meaning to ask: have I overlooked the command to start
> a project parse manually (instead of after opening a project), or is there
> indeed no such option? I've tried running without automatic
> parsing-after-project-opening for a while to see if that changed things,
> but found it too cumbersome to have to initiate a manual parse (by forcing
> a problem report update) just to have documentation tooltips.
> (There's an OT implicit question in here: why is the cached parsing info
> not used, or why waste space caching it if it's not used?)


You have a "Reload" entry in the Projects toolview context menu.

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20141107/498a2443/attachment.html>


More information about the KDevelop mailing list