Re: [AC21.5] segfault during compilation
On 9/15/05, Marcus Crestani <crestani(a)informatik.uni-tuebingen.de> wrote:
This is probably a memory corruption bug, debugging these is a real
pain in the ass... However, you should be able to set a watchpoint on
this slot of the lookup table and see what writes the 0x3 to it.
Btw, this seems to be NOT a compiler bug. I recompiled it with -O0
and nothing changed.
Marcus, if our theory is that it is a memory corruption bug -- when
you run valgrind on your machine -- does it say that xemacs is clean?
--alexm