Re: Back trace of 21.5-b1 "anise" crash
>>>> "Ben" == Ben Wing <ben(a)666.com>
writes:
> (gdb) where
> #0 0x403c8801 in __kill () from /lib/i686/libc.so.6
> #1 0x080b453b in fatal_error_signal (sig=11) at emacs.c:535
> #2 <signal handler called>
> #3 0x080911b3 in bytecode_arithop (obj1=25, obj2=0, opcode=Bplus) at bytecode.c:387
Ben> very strange. `25' and `0' look like numbers that somehow failed to get
Ben> make_int[]ized.
Ben> martin, this is your area of expertise.
Ben> thoughts?
It looks to me like we have a Lisp_Object that is all zeros. That
should never happen. The most likely reason is that there is a bug
(elsewhere!) that is causing memory corruption of the stack. Most
likely a bug in a C function called from the currently active lisp
function. There is a chance you can get a lisp backtrace from a C
debugger - see src/.gdbinit.