[lazarus] Crashes with Lazarus IDE
acjgenius at earthlink.net
Thu Sep 25 16:56:42 EDT 2003
I don't. This isn't just about the logging, this is about the everything dies and there is no autosave no gracefull exits it just dies out from under you. I want a way to keep going at least long enough to save everything whenever possible, this isn't possible from the interface the way it was in most places, and this is the reason there were already push/pops in a few other locations prior to this where it was aespecially likely to happen.
When some problem happens after working on something for 20 minutes and not having saved then what? oops all data out the window because gdk burped a bad window? If I am wrong fine, revert, but I don't see anyway of handling them safely otherwise.
From: Marc Weustink <marc at dommelstein.net>
Sent: Sep 25, 2003 4:47 PM
To: Andrew Johnson <acjgenius at earthlink.net>, lazarus at miraclec.com
Subject: Re: [lazarus] Crashes with Lazarus IDE
At 19:24 25-9-2003, Andrew Johnson wrote:
>OK what I have done.
>I couldn't reprocduce or find what this might be, but I went ahead anyway
>and made the whole gtk interface trap gdk errors around calls to gdk
>functions that use windows(and I think I got a bit carried away in a few
>points and put it around colormap and visual stuff) I may have missed some
>but overall anything that is possible to cause bad drawable errors from
>the interface directly should be caught.
Hmm.. I think this effectively bypasses the logging and exception
generation I'd implemented in gtkobject.inc.
The way it was implemented one didn't need extra push and pop code.
OK if you hit a bad drawable or so the application exits, but at least one
could look at the callstack before it happens.
If it is only for the ability of a backtrace and/or an Exception, I vote
for the way it was.
To unsubscribe: mail lazarus-request at miraclec.com with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
More information about the Lazarus