https://bugs.freedesktop.org/show_bug.cgi?id=73464
--- Comment #17 from Michael Meeks <michael.me...@collabora.com> --- Stuart; the trace would be best done with the symbol server setup (or somesuch) I guess - or a build that has symbols; there is no good data there: *** ERROR: Symbol file could not be found. Defaulted to export symbols for vcllo.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for sofficeapp.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for soffice.bin - Cannot find frame 0x9, previous scope unchanged ... are not good signs from that perspective. Beyond that - it looks like a heap corruption: these are exciting bugs to track on Windows. I'd recommend running it under: http://drmemory.org/ which makes it 40x slower or worse, but should catch the problem in a helpful way - it'd be fantastic to have some output from drmemory for this specifically - and ideally with symbols. With a drmemory trace (as with valgrind) it should point is ~directly at the real bug =) Thanks so much for chasing though ! -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
