btw as for those 37000 stack frames when marking a list, kkcc has a simple form of tail-recursion built into it that should ideally handle lists without any stack recursion. if that's not working it should be easy to fix it. (right, mike?) ------- Original Message ------- On Fri, 20 Dec 2002 19:39:26 +0900 Stephen J. Turnbull?wrote: FUT xemacs-beta. >>>>> "Ben" == Ben Wing <wing(a)666.com> writes: Ben> i did test this non-kkcc. in fact i tested it in quite a Ben> number of configurations, so i'm surprised to see that it Ben> broke. how did it break? Well, for starters the MS-only (?) functions strupr and strlwr were left naked in lisp.h, breaking the link. The crash I'm getting is Fatal error: assertion failed, file /coda/Software/XEmacs/21.5/src/alloc.c, line 3323, GCLI_lh != 0 #5 0x080ea8e7 in assert_failed ( file=0x830d200 "/coda/Software/XEmacs/21.5/src/alloc.c", line=3323, expr=0x830de6a "GCLI_lh != 0") at /coda/Software/XEmacs/21.5/src/emacs.c:3624 #6 0x08093ae2 in mark_object (obj= {gu = {type = Lisp_Type_Record, val = 35288680}, s = {bits = 0, val = 70577360}, u = {bits = 0, val = 70577360}, ui = 141154720, i = 141154720, v = 0x869d9a0}) at /coda/Software/XEmacs/21.5/src/alloc.c:3323 followed by about 150 frames of mark_foo(), details on request. Is this symtomatic of broken union-type? This is a --use-union-type build. I see this particular assert a fair amount myself, and occasionally in backtraces on xemacs-beta. I'll try with --use-union-type=no. Ben> one more thing ... you're not using union-type, are you? i Ben> get crashes galore in pdump with both gcc and vc++, using Ben> union type. see all my messages about this. It would be nice to have real bug reports (ie, >= C backtrace) on this stuff so that (a) we can guess whether we're seeing what you've seen and (b) we can pass it on to the GCC core developers who occasionally contribute to XEmacs. -- Institute of Policy and Planning Sciences 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.