vi: Don't let uninitialized data pass as a response for SetBufferCount
Currently SetBufferCount doesn't write to the out buffer which then contains uninitialized data. This leads to non-zero data which leads to responding with different error codesmaster
parent
8f548266cd
commit
03a6f3b0f4
Loading…
Reference in New Issue