Re: Argh! What am I missing with MULE build? (21.0-b64 + Solaris 2.5 .1 + EGCS 1.1.1)
>>>> "G" == Gunnar Evermann
<ge204(a)eng.cam.ac.uk> writes:
G> please use src/gdbbinit as you ~/.gdbinit file and use the 'pobj'
G> command to print the 'obj' variable in stack frames 3-8.
> #0 0xef0748e8 in kill ()
> #1 0x95748 in fatal_error_signal (sig=11) at emacs.c:262
> #2 <signal handler called>
> #3 0x4c424 in mark_object (obj=541561856) at alloc.c:3170
> #4 0x6f21c in mark_char_table (obj=2, markobj=0x4c310 <mark_object>)
G> ^^^^^^
G> Ouch, I doubt we have a valid object at address 2! :-(
> at chartab.c:145
> #5 0x4c4a0 in mark_object (obj=541825024) at alloc.c:3180
> #6 0x4c684 in mark_object (obj=4970372) at alloc.c:3234
> #7 0x4c600 in mark_object (obj=3956736) at alloc.c:3216
> #8 0x4e598 in garbage_collect_1 () at alloc.c:4493
We still have a memory corruption bug that is going to be a challenge
to track down. In addition to using src/gdbinit, It might help to use
the watchpoint feature in your debugger, if available. Also,
judicious use of always_gc might be useful. This bug will be tough to
find, but you'll be a hero!
Martin