Mohammad Atikur Rhaman

Okay. we'll definitely looks on those point.

Thank you, we'll try to figure out how to set our exception mask as needed in our code.

Sorry for the late reply, I couldn't get back to this issue due to other priority work. We’ve traced down floating point exception masks at the initialization of our project. We’ve found [exInvalidOp,exDenormalized,exZeroDivide,exOverflow,exUnderflow,exPrecision] this set of exceptions is already masked on our project. For more confirmation we’ve created a new VCL application and traced down floating point exceptions. This time the set was [exDenormalized,exUnderflow,exPrecision]. Could you please tell us if there is any project setting or something that we can remove the ‘exZeroDivide’ exception from this set or get back to the default floating point exceptions?

Could you please tell me how to identify the DLL that changes the floating point control status to mask exceptions. Reiterating that this issue occurring after we mover our project form Delphi Seattle to Delphi Sydney. our project was working fine on Delphi Seattle.

But previously at Delphi Seattle IDE it was working fine. It stopped working when we moved to Delphi Sydney IDE.

It doesn't throw exception on zero divided zero scenario.

Our target is Windows 32 bit in the IDE

Our project was throwing "Divided by zero" exception fine when we were in Delphi Seattle IDE. Now As we have moved to Delphi Sydney IDE, the exception is no longer working, instead of that variable is now being set to INF. We have tried the exception mask to enable the exception but that doesn't satisfy our requirements. Is there a better solution than this like changing IDE , compiler or project setting?