https://bugs.documentfoundation.org/show_bug.cgi?id=82430
--- Comment #40 from drmme...@hotmail.com --- (In reply to Michael Stahl from comment #39) > 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. I will admit I know little about debugging. Typically in cases where SSE2 is the issue it is because the compiler was set to use that instruction set and a rebuild clearing that option can fix it. Sorry, but I was just a big put off that I spent a log of time bouncing against this bug and the tone of this thread makes it appear that fixing it is a low priority. It should be pointed out that System Requirements say: "Pentium-compatible PC (Pentium III, Athlon or more-recent system recommended);" The P3 was an non-SSE2 processor. I wonder how many people assume LO should work because of this, and then when it doesn't they just move on to a different program. -- 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
