Re: Back trace of 21.5-b1 "anise" crash
>>>> "Martin" == Martin Buchholz
<martin(a)xemacs.org> writes:
>>>> "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
Ben> failed to get make_int[]ized.
Ben> martin, this is your area of expertise.
Ben> thoughts?
Martin> It looks to me like we have a Lisp_Object that is all
Martin> zeros. That should never happen. The most likely reason
Martin> is that there is a bug (elsewhere!) that is causing memory
Martin> corruption of the stack. Most likely a bug in a C
Martin> function called from the currently active lisp function.
Martin> There is a chance you can get a lisp backtrace from a C
Martin> debugger - see src/.gdbinit.
Anything I can try/do/remember now, or if this happens again?
Step by step idiots guide only please - suggesting I run the
slapcrackboozleomatic test (or whatever) will make me cry :-)
Cheers.
Baz.
--
Barrie J. Bremner OpenPGP public key ID: 5164F553
baz [at] barriebremner.com http://barriebremner.com/