Re: [Bug: 21.4.14] Fatal error: assertion failed, file xlwtabs.c, line 1997

Nick> Further information re this bug (sorry - I forgot to include Nick> it with original report). Something very strange is going on there. Immediately before the assert, the function PreferredSize3 is called. The last thing it does is *reply_width = Max(wid, MIN_WID) ; *reply_height = Max(th+hgt, MIN_HGT) ; where MIN_WID == MIN_HGT == 10. wid, th, and hgt are Dimension, reply_width and reply_height are Dimension*, so there should be no signed/unsigned braindamage, either. The pointers reply_height and reply_width are passed down from function to function unchanged, so that assert should be impossible to trigger. :-( If you still have the core, could you inspect the values of reply_height and reply_width in the last few frames *reply_width and *reply_height? I sorta suspect a compiler bug. The only other possibilities I know of would be if the stack got smashed and pointer aliasing, but there's nothing that could get called from there that could smash the stack and the pointers aren't aliased. Nick> #0 0x00239c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 Nick> (gdb) A stack trace would be nice. Red Hat probably provides a debugging package for XEmacs, which will allow you to get the symbols (such as the names of the function parameters). Without those, the stack trace isn't much use. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.