Marc Weustink wrote

It is not realy a GTK bug, it has something to do with events still firing. Some examples don't have this problem.

Yep. For example, this error does not appears, when you will create just one form. But will be, if more that one... I'm usually do:

procedure tform.onclose(s:tobject);
begin
  if application.messagebox('Are you sure to exit?','',$34)=6 then halt;
end;

...and running my program with stdout to /dev/null *inside* the Lazarus program.
And user does not see the seg. fault and 'core' file. But this bug is still present ;(

M.B.M

It is a GTK-like bug, I mean. All of the programs do same thing for now... :-(

If you compile with -gl then you'll get the source lines also. Since yesterday the backtraces should be correct also for exceptions generated by signals.

Peter

Hi all,

I've been playing with some of the GTK demos under the Lazarus directory. I have noticed that every time I exit one of the demo's I get the error:

An unhandled exception occurred at (hex address) : Access violation

Is this a bug in the Demos causing this? Or just an incompatibility between GTK and Windows? Lazarus also does the same thing when I try to exit it.

Thanks for the assistance,

Chris

+ From: On Behalf
+ Of M.B.M

+ Chris Moody wrote:
+
+ > An unhandled exception occurred at (hex address) :
+ > Access violation
+ >
+ > Is this a bug in the Demos causing this? Or just an
+ > incompatibility between GTK and Windows? Lazarus
+ > also does the same thing when I try to exit it.

+ It is a GTK-like bug, I mean. All of the programs do same
+ thing for now... :-(

It is not realy a GTK bug, it has something to do with events still firing. Some examples don't have this problem.

Marc

+ From: Peter Vreman

+ If you compile with -gl then you'll get the source lines also. Since
+ yesterday the backtraces should be correct also for
+ exceptions generated by signals.

Ah, great !

Marc