Critical Bug in VS 2015 SP1: Modulo 0 leads to a crash!

[Krid]

Hello,

we just discovered that performing a Modulo 0 operation in a realtime sequence crashes VeriStand 2015 SP1:

• A PharLab realtime target is immediately restarted
• On Windows VeriStand crashes with the following message:
  

I'm aware that Modulo 0 is an undefined operation but a bug in a realtime sequence should never crash VeriStand (this can lead to dangerous situations).

I know that NI normally fixes bugs only in the next release/service pack but I hope you agree that a bug of this magnitude deserves an extra hot-fix!

I have attached a sample realtime sequence that triggers a crash/restart.

[OlegS]

Dear Krid,

I’ve just reproduced this issue and I’m absolute agree with you.

So I also created an CAR Request #595607.

I hope it will be fixed soon.

Kind Regards,

SG3 | Staff Applications Engineering | National Instruments | NIG |