On Thu Jun 29 13:40:48 2023 +0000, Vladislav Timonin wrote:
Don't remember, think it was us, current implementation wise (I know, shouldn't rely on that too much), it's a pointer to a heap allocation, which I assume can't have `0` as a valid value.
I'd say the heap allocation thing is a hack in Wine. It looks like Windows have sequence numbers for cookies instead. If we ever have an app that relies on `0` being returned on newly created threads or fibers, then we won't be able to fix the app without regressing, until all callsites that assume `0` is an invalid cookie is fixex.