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.
GetErrorName() with bad arguments
- airsoftsoftwair
- Posts: 5833
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: GetErrorName() with bad arguments
Right, clearly a bug, will be fixed.
- airsoftsoftwair
- Posts: 5833
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: GetErrorName() with bad arguments
Code: Select all
- Fix: Memory access fault when passing invalid error codes to GetErrorName() and SysBase.GetErrorName()