https://bugs.documentfoundation.org/show_bug.cgi?id=82430
--- Comment #39 from Michael Stahl <mst...@redhat.com> --- it's not obvious where the remaining problem is, none of the developers has such old hardware, and to have any hope of making progress we would need to locate the faulting instructions with a stack trace from windbg or VisualStudio. for windbg there are some instructions on this here, but i don't know if it stops automatically when an invalid instruction is executed or if that needs some special commands... https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg in Visual Studio there is a dialog in "Debug->Exceptions" with a lot of checkboxes about which should stop the execution, there is under "Win32 exceptions" the "0xc0000001d Illegal Instruction" which i guess should be enabled. -- 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
