Skip to content
Discussion options

You must be logged in to vote

Why is StreamReceiveComplete called in the receive callback? That's only necessary with asynchronous receive completion (returning QUIC_STATUS_PENDING from the receive callback).
Also, SafeStreamSend has a bug where the send_buf needs to be part of the SendContext struct. In the code pasted above, it is allocated on the stack, and a pointer to the stack address is given to MsQuic, but once SafeStreamSend returns, that address is no longer valid, but MsQuic may read it after then.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@realurl2077-netizen
Comment options

Answer selected by realurl2077-netizen
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants