On Wed, 21 May 2025, Jeremy Drake via Cygwin wrote: > the child to not be very fruitful, but maybe there's some debugging to be > done there Well, found the bug that results in a 0 size. size is a DWORD, but mb.RegionSize is 0x200000000. mb.RegionSize is SIZE_T, but I figure size_t is appropriate.