Project

General

Profile

Bug #4767

memptr set-size() issue

Added by Greg Shah almost 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:

History

#1 Updated by Greg Shah almost 4 years ago

From Marian:

memptr, set-size - on Windows when passing a negative number the value apparently gets set as xor between max unsigned int and the absolute value passed as input, since that is always higher than the max integer it should throw and error and in version 12 a new error number was added 19208 although if passing a positive value greater than the max integer (signed) it throws the 15747 one just like it is already in FWD. Oddly enough when trying to reproduce the behavior again this morning on 11.7.4 the size of memptr when using negative values remains zero, no idea if the same thing happens on *nix though.

Also available in: Atom PDF