I received a crash message from a MadExcept user from a user. The exception was an invalid floating point operation.
The odd part is that the callstack is dying at @FSafeDivide.
I did google and found out that this is a check of some pentium chips that didn't do the division correctly. If the test fails, all units will run in software, not hardware. I have the FDIV option for Pentium-Safe enabled in my compiler settings.
Could this cause an error? I also read somewhere that EInvalidOp, which was an exception class, could be a stack overflow or something like that.
There is a dream of a madman here, except for a message if you want to read it.
exception class: EInvalidOp Exception message: Invalid floating point operation.
thread $1014 (TMyBossThread):
00403509 M5b3.exe System @FSafeDivide
008300c9 M5b3.exe MMyWorkerThread 317 TMyBossThread.Search
0073e87a M5b3.exe MMyManagerThread 186 TMyWorkerThread.Execute
008e8c17 M5b3.exe madExcept HookedTThreadExecute
0042c150 M5b3.exe Classes ThreadProc
00405354 M5b3.exe System ThreadWrapper
008e8af9 M5b3.exe madExcept CallThreadProcSafe
008e8b63 M5b3.exe madExcept ThreadExceptFrame
created by main thread ($864) at:
0073e828 M5b3.exe MMyManagerThread 171 TMyManagerThread.Create
source
share