Calling UpdateTicks in quick succession could lead to division by zero. Added explicit check to avoid this.
Timers with 0 frequency would lead to division by zero while calculating realtime information. Skipping realtime information in this case now.
GPU Timer internally would divide by zero in a handful of cases. Guarded by trapping exceptions.
This was found while testing nxdk-rdt which can lead to half-initialized hardware and bogus reads in some cases. As nxdk-rdt does not support api.call you have to disable timers.append(RDTSCTimer()) which depends on it to reproduce my test. Also depends on #59.
I found some issues with this script:
UpdateTicksin quick succession could lead to division by zero. Added explicit check to avoid this.This was found while testing nxdk-rdt which can lead to half-initialized hardware and bogus reads in some cases. As nxdk-rdt does not support
api.callyou have to disabletimers.append(RDTSCTimer())which depends on it to reproduce my test. Also depends on #59.