Stephan Bergmann wrote:
Looks like some sort of memory corruption, leading to deletion of a memory block at address 0x6, detected by your libc and causing an abort. Try valgrind'ing it.
Hi Julien, to slightly expand on that - http://wiki.documentfoundation.org/BugReport#How_to_get_valgrind_log_.28on_Linux.29 has some howto for valgrind. Valgrind's memchecker may spot the problem *much* earlier, thus potentially flagging the buggy code directly. If you want to inspect things in a debugger then, --db-attach=yes will prompt you each time valgrind finds an error. HTH, -- Thorsten
Attachment:
pgpfhEvRsQIPD.pgp
Description: PGP signature