Open kolumb opened 3 years ago
ah, I think I know what the cause is; previously we never used the "native stack" (rsp
, rbp
) for anything, so it was basically always 0-filled.
But #395 also started to push stack frames (for stack traces in debuggers), so now the native stack has stuff on it. I just translated the bm stack stuff to the new convention and didn't really check the windows stuff, sorry.
WriteFile function needs fifth argument that it takes from the stack, according to Microsoft x64 calling convention. Previously it was always null. After changes in #395 it started to take garbage pointer from stack and try to write there. Found that it's fixed if I make this change:
But I not sure if this is a root cause. Also maybe it makes sense to implement testing before fixing.