On Tue Nov 7 08:28:50 2023 +0000, Huw Davies wrote:
These are returned to the caller, so this is changing the ABI.
That's an interesting point. These values are presumably supposed to be freed with NsiFreeTable, but the caller could try to free them with HeapFree instead. Is there any good way to tell which allocation function Windows is internally using here?