https://bugs.documentfoundation.org/show_bug.cgi?id=93953
Michael Meeks <michael.me...@collabora.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #8 from Michael Meeks <michael.me...@collabora.com> ---
Can't reproduce with windows 32bit build from 37a04c46c5de7. Nor on Linux with
- 32ab58fb0bbe7e76536758de66e4fb13f4870ef.
Trace looks like stack corruption of some sort - nasty to chase that; its
possible but unlikely that a valgrind trace would help. I would suspect Java
too for this sort of case FWIW ;-)
Then again - quite possibly the segv you get in gdb there is one that Java
creates, expects and handles (java uses SEGVs for various reasons) - can you do
'continue' and if it doesn't exit but crashes again - get a new backtrace ?
When you say it crashes - were you using a SEGV under gdb to mean a crash ?
they are far from all crashes =)
--
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
