>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
> --==> "SY" == Steve Youngs <youngs(a)xemacs.org>
writes:
SY> I've seen this a few times now. Trying to view certain
SY> messages in Gnus causes XEmacs to dump core with this error:
SY> Fatal error: assertion failed, file print.c, line 1480,
SY> abort()
SY> The attached message, a post from Mike Sperber to
SY> xemacs-patches, triggers this bug.
Looking at your earlier report, it's a Beavis and Butthead crash, ie,
XEmacs was already going down, and then triggered an assert in the
process of trying to report the first problem. In this case, the file
identifier is the same, presumably it's supposed to be stderr.
Since 0x6 is an itty-bitty number but we're trying to access memory, I
wonder if there's some FILE* vs file descriptor confusion in Ben's new
error reporting code?
I'll try to look at it later, but maybe that helps. If you've got a
core file, start gdb, source src/.gdbsrc, and use pobj to get the
objects that are being passed to funcall and friends. See frames 14
and 15 in the trace in your earlier report. Frame 12 is bogus, there
are no lisp objects living at address 0x2. Also check constants_data
in frame 13.
--
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.