Marcus Crestani <crestani(a)informatik.uni-tuebingen.de> wrote:
Valgrind complains about some Lstream-related invalid reads, but
nothing concerns the new allocator. You'll probably see the same when
you run valgrind on the other system you mentioned where XEmacs works.
Since this is so repeatable (and XEmacs hasn't even been dumped,
yet ;-), Hrvoje's watchpoint suggestion is the best way to debug this.
[ Of course, I'm assuming that hardware watchpoints are available, and
tbey should be, since we're talking 32-bit x86 linux. ]
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.