Page 1 of 1

GetErrorName() with bad arguments

Posted: Fri Feb 16, 2024 10:41 am
by Flinx
I accidentally set a variable to True in certain situations, which should be displayed later using GetErrorName().
So I noticed that GetErrorName() causes a memory access violation when it is called with positive values.

Re: GetErrorName() with bad arguments

Posted: Mon Feb 19, 2024 9:32 pm
by airsoftsoftwair
Right, clearly a bug, will be fixed.

Re: GetErrorName() with bad arguments

Posted: Thu Jul 18, 2024 7:42 pm
by airsoftsoftwair

Code: Select all

- Fix: Memory access fault when passing invalid error codes to GetErrorName() and SysBase.GetErrorName()