New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug(message_ex::copy): In some case, the message_ex::copy function will trigger an assertion #1937
Comments
@Sunflower876 Thanks! Have you encountered such a check failure? Could you please leave some logs here, a backtrace would be better. |
|
|
The first format is the Thrift message format, used for communication between client and server. The second format is the RDSN message format, used for communication between servers. The second format calling message_ex:: copy will definitely crash. |
I saw the crash is caused by request |
Bug Report
There are two formats for message_ex, one is that both the header and body are saved in the buffers field, and the header and buffers [0] are the same. the other format is that the header is not saved in the buffers field and exists separately. In the message_ex::copy function, total_length represents the sum of the lengths of the header and body. However, in the second case, i only counts the length of the body, so checking that i and total_length are equal will fail.
The text was updated successfully, but these errors were encountered: