==== skip to ==== for post.
First up about 10 years ago, I got asked what would your ideal IDE do?

Half an hour of brainstorming got half of what Kdev4 does and a tiny bit it does not. (It is not VR(yet) for start...) I had half an idea what it would be like to work in an environment that was trying to help. So much more of the code monkey is now gone than even I imagined might be. Holding the N most recent variable names in short term recall memory is no longer required to be in the flow.

simply magic.

Tips hat.
Much love.
As many kisses as you like.
... rocks your boat.

===========
Anyway ever since I first used Kdev4, the background parsing has crashed
whenever I have the code for a particular project open.
The crash is stable across N versions, but I do have to wait a bit.

(stable means, any version kdev4 that Ive used: unload that project zero crashes. Turn off parsing zero crashes.
The Project Compiles Clean, its not some arbitrary piece of gobble de gook.
Its not template meta programming. There is hoopy conditional preprocessor token pasting CDEBUG magic.
)

I could drag my self up to the latest release and submit a core file/ blah blah, as per the std instructions? That might or might not make it obvious what happened.(currently on 4.2.0)

Instead I am prepared to

Would someone be specifically interested if I can binary search my library
and find a smaller example of (probably)
(based on whats the hoopiest code in the lib)

This macro magic makes background parser go boom?

Who works on background parsing in kdev4?

Yeah of course its free so you want it. But will someone use it? it may going to take me longer (days?) to cut it down than it will take to fix whatever, once I find a simple this crashes that (after a few minutes) test case.


On other projects I _was_ prepared to work on, I've been burnt wasting time on bugs is OS projects that then just get denied, as being 'no that is a feature...', I currently love you guys I don't want to lose that.

Alan