I'm starting to do some LibreOffice development, will KDevelop work with it?

I'm on Fedora (16, 64x86), using KDE not Gnome, and installed KDevelop from the repository and opened the top level LibreOffice makefile... about four hours ago. The KDevelop window is still frozen, but the system monitor is showing negligble processor activity (6-10% on each cpu), KDevelop is showing as using about 78M of RAM & 51Mb of shared memory, KDevelopAttach is present but only using about 186k or RAM.

Has it hung?
Does it have any hope of being able to work with the enormous project?

I managed to get Eclipse to index it, once, it says there are 27,836 source files, 37,203 header files, 4,332,116 declarations and 31,013,280 references, so it's a very big project. Eclipse looks like it's not really going to work. NetBeans couldn't even index it.


Mark

nothing I'm familiar with (inc Kdevelop) but I would suggest you query on LibreOffice's development irc channel to see how the dev's develop.

google01103 wrote:nothing I'm familiar with (inc Kdevelop) but I would suggest you query on LibreOffice's development irc channel to see how the dev's develop.

The devs develop with vi, vim, emacs, gdb, and terminals. I'd really rather not do that, though if nothing else is man enough

If you attach gdb, are you able to get a trace? It sounds like KDevelop could very well be hung, or at the very least - slowly processing the sources...

Sounds like a bug (in the makebuilder support), or a faulty installation. Isn't libreoffice written in Java? KDevelop does not have java language support, so it's not parsing the sources. Try to get a backtrace by running KDevelop through gdb and interrupting it when it's stuck.

The limitation with huge projects is memory size, so as long as you don't run out of memory large projects are no problem for KDevelop whatsoever (except that it might take a while to parse them -- but that'll run in the background and display a progress bar in the corner). What you describe is a bug in any case.

Greetings

It appears that it had hung, I had a chat with someone on the IRC, we attached dbf, got a trace and it seemed that it was blocked. The age-old solution of killing it and restarting got a bit further. At least for a while I had a responsive UI and it was indexing.

However, after some time (a few hours?) KDevelop had "disappeared", and KDE-the-desktop was looking really unstable, so I rebooted the machine.

I can see session directories, and files in those directories, but that's about the limit of my expertise, at the moment.

Libre/Open Office is written in C++, hence my interest in KDevelop.

It seems a shame/odd that there doesn't appear to be an open source IDE that can handle, well, it seems to me exactly the type of project that would most benefit from it, a really big one. It seems that a shift in strategy would be required to deal with such a beast, being dependant on such a finite resource as RAM is not a good thing in this context.

Anyone want to help make it work?

Regards
Mark

Ok, an update, it's working a bit.

Setting the "reduced parsing" file limit to 100k files instead of 300k (KDevelop says LO's got 308k files) stops it indexing! Which at least lets it work at the editing level.

MarkRS wrote:...stops it indexing! Which at least lets it work at the editing level.

... and which makes it about completely equivalent to kate with a different toolbar layout, and thus rather pointless.


What did you do exactly?

I just downloaded the libreoffice-core archive from the website, and KDevelop is currently happily parsing it. It'll surely take a while (although not more than maybe 30 minutes!), but it does not crash or get slow or anything.

Which archive did you open as a project?

and which makes it about completely equivalent to kate

One of my main wants, I suppose, is integrated, ui based, debugging, which this route still gives me, doesn't it?

What did I do? I started the "Pick a session" version of starting KDevelop and picked "New Session", and then pressed "Stop" when it started up, and thus started indexing.

I'd also lowered the "reduced parsing" limit from 100,000 files to 10,000, although the original limit should have reduced parsing of this project (308,0000ish files).

I managed to set a breakpoint and stop the code when it reached it, so things are looking good, however...

1) I must remember not to let the debugger run through window interaction control. I don't think that's a shortcoming of KDevelop, just of a UI based debug, that's fair enough.

2) I have no luck re-opening a previously saved session. It seems to just hang. I've run it through gdb so that I can get some kind of stack trace. I have now filed a bug for this, 297319.

No, I'm wondering which code base you're trying to open, as I had no problems with openoffice core -- no hangs, no slowness. Could you provide a link for the same download you have?

I followed the instructions on the "How to build" page, cloned the master with

git clone git://anongit.freedesktop.org/libreoffice/core libo

and then checked out the release branch with

git checkout -b libreoffice-3-5 origin/libreoffice-3-5

I also downloaded only the core sources (although not master), and it happily parses them.
Can you attach a debugger when it hangs, and also, can you watch your memory usage? How much system memory do you have, btw?

Greetings

After some discussion on the IRC channel this seems to be an issue with my system not KDevelop.

I had filed a bug, https://bugs.kde.org/show_bug.cgi?id=297319 and attached a stack trace in there. What I was seeing was that there was no KDevelop cpu activity.
I have now updated the bug report.

It appears that the problem is to do with gam-server, and seems to be a known issue, https://bugzilla.redhat.com/show_bug.cgi?id=786170.
As per the bug report on RedHat, when I kill the gam server, even though it fires up again immediately, it does allow KDevelop to get on with my life.
I'm now very pleased with KDevelop

Since you ask I've got 6Gb of RAM in this machine.