Hi Vincent,
On Thu, 2010-09-02 at 15:57 +0200, Vincent Lefevre wrote:
> (gdb) thread apply all backtrace
Ok - that's quite helpful. Probably the bug is more banal than a
complex threading problem: a simple memory corruption breaking the
(thread safe anyway) heap primitives.
Is there any chance you can install the cups and openoffice debuginfo
packages (so we get a better trace), and run it under valgrind [ this
will take a while ;-]:
cd /usr/lib/ooo3/program # [or Debian equivalent]
export OOO_FORCE_SYSALLOC=1
valgrind ./soffice.bin -writer 2>&1 | tee /tmp/val-log
And send in /tmp/val-log ( probably best compressed unless you can
supress the runaway java nonsense ;-). Hopefully that will pin-point the
heap corruption to the line.
Many thanks,
Michael.
--
michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot
--
To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1283764429.14362.10.ca...@linux-iwk5.site
