Re: W3 crashes
Martin Buchholz <martin(a)xemacs.org> writes:
Jan> There is a fix, but you vetoed it :-). This is caused by the
Xaw3d/Xaw
Jan> breakage. Compile with plain athena as a work around.
Hey, I didn't realize this was a bug fix!
It looked that way before, but I wasn't sure. You must have missed the
thread about this on XEmacs-beta before. I already thought it was
kind of ironic that I design a work around configure thing; Somebody
is so helpful as to actually implement it and then he gets vetoed :-)
I was trying to avoid introducing a DE-stabilizing change into
XEmacs. How come this crash hasn't always been a problem?
1. Before the Xaw3D auto detection stuff there weren't that many cases
of people compiling with Athena3D _and_ executing glyph-test.el
2. The crash is when creating a progress bar widget (It is easily
reproduced by executing the progress bar example code
fromglyph-test.el). Until the latest W3 came around no code
actually used those.
Expect more crashes as the widget code slowly gets exercised.
I'm not convinced yet that it's an Xaw/Xaw3d mixup yet,
though.
Here is the evidence:
0. When you investigate the crash with a debugger, you can see that at
that point the widgets structures are filled completely wrong
1. It goes away if you force compiling/linking with plain Xaw.
2. The progress bar widget subclasses the Xaw label widget.
Subclassing is _exactly_ what goes wrong if you use the wrong
headers.
3. Note how xlwgauge.c explictly uses _ThreeDP
Jan