Hi Marcus,
On 9/13/07, Marcus Crestani <crestani(a)informatik.uni-tuebingen.de> wrote:
This very much looks like valgrind complains about the memory
protection caused by the incremental garbage collector.
Did you start valgrind with the option
`--vex-iropt-precise-memory-exns=yes' to enable the magic that allows
valgrind to work with the write barrier's signal handlers?
Ah, there's what I was missing, thanks. Still, valgrind is issuing
quite a large number of complaints, including memory leaks. I'll
check them out.
Thank you!
--
Jerry James
http://loganjerry.googlepages.com/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta