Re: failed assertion and core dump

Elisabeth> BTW, gdb has this to say about the core dump: Elisabeth> (gdb) where Elisabeth> #0 0x28476b0c in kill () from /usr/lib/libc.so.4 Elisabeth> #1 0x807422c in XMapRaised () Elisabeth> #2 0xbfbfffac in ?? () Elisabeth> #3 0x8075eb6 in XMapRaised () Elisabeth> #4 0x810730b in matherr () Elisabeth> #5 0x810884c in matherr () Elisabeth> #6 0x807a3be in XMapRaised () Elisabeth> #7 0x807a4bb in XMapRaised () Elisabeth> #8 0x805aa85 in XMapRaised () Elisabeth> #9 0x807aed6 in XMapRaised () Elisabeth> and then the XMapRaised calls repeat ad infinitum (at Elisabeth> different addrs). This looks like a smashed stack to me, and Elisabeth> re-search-forward("</?[A-Za-z_][^>]*>" nil t) regexps are one known way to cause stack overflows. It could be a wanderlust bug. Unfortunately I don't have XEmacs 21.1 or wanderlust installed at the moment so I can't test quickly. Unless somebody else does, it will take some time to debug this. However, if it is an XEmacs bug, it will not be fixed in the 21.1 series (there probably will not be another release in that series). So you may as well try XEmacs 21.4, I'd say. BTW, the huge Lisp stacktrace is simply due multiple copies of wanderlust's cache of message information. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py