Hi Lazarus Team,
I've been working with Lazarus for 4 weeks now to see, whether it can be an alternative to commercial IDEs, and whether it is suitable for commercial development (that's where time matters, and the results need to look great), and I must say, I am impressed, considering that this is a free project Lazarus has reached an astonishing level.
Nevertheless there are still serious drawbacks, one of them is an unnerving instability in the IDE: every now and then, say 1-4 times a day, it does crash for no apparent reason. In rare cases there is a message (something like "file missing", or "file not open" - cannot remember which one, and a filename is never given), sometimes there are SIGSEVs, sometimes I get just program hangs and I must terminate using the operating system.
The damage done is never very big, it seems that Lazarus has a very capable "parachute", so I can almost always fire up the IDE again and continue work without loosing more than a line or two of my last entries, nevertheless it is an unnecessary annoyance if one cannot trust his IDE.
I am aware that such vague informations help nobody, so I think about ways to be able to provide more accurate information. If I'd compile Lazarus with Debug ... and if it crashes ... can I somehow attach a debugger to the program, as long as it is still in memory, and try to extract the exact location of the crash, and the call-stack?
Thx, Armin.