nn(a)uswest.net writes:
> M-x w3 caused xemacs to crash
Do you get this consistently? If you can reproduce can you find the
out the exact lisp call that is causing this?
> #3 0x81c46d5 in MaxLabel (gw=0x8583338, wid=0xbfffd248, hgt=0xbfffd24a,
> w0=0xbfffd24c, w1=0xbfffd24e) at xlwgauge.c:967
if( lbl != NULL ) {
---> lw = XTextWidth(font, lbl, strlen(lbl)) ;
w = Max( w, lw ) ;
}
Could you check whether the font and lbl have sensible values in this frame?
> #4 0x81c32cc in GaugeResize (w=0x8583338) at xlwgauge.c:327
> #5 0x4002f99b in Initialize () from /usr/X11R6/lib/Xaw95/libXaw3d.so.6
> #6 0x40130185 in CallInitialize () from /usr/X11R6/lib/libXt.so.6
> #7 0x4013014d in CallInitialize () from /usr/X11R6/lib/libXt.so.6
> #8 0x401306a2 in xtCreate () from /usr/X11R6/lib/libXt.so.6
> #9 0x40130b8f in _XtCreateWidget () from /usr/X11R6/lib/libXt.so.6
> #10 0x40130cb0 in XtCreateManagedWidget () from /usr/X11R6/lib/libXt.so.6
> #11 0x81bd434 in xaw_create_progress (instance=0x8583158) at lwlib-Xaw.c:808
It is making a new progress bar. This is still very new functionality.
I think Andy and E. Falk would love it if you could find out a simple
case causing the crash.
Jan