-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
evbuffer use after free #1564
Labels
Comments
This means that the bufferevent had been used after it freed, but of course this should never happen. You told that you stripped your application code frames from the stacktraces, then I will recommend you to do though your code, precisely look at from which place |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're using libevent in an application, that can end up with thousands of threads (wheeeee). We've gotten a bunch of segfaults in libevent code, so I finally tried using clang's thread and address sanitizers (macOS). The address sanitizer gave me an instance where (as the title says) a buffer is used after free:
(I removed our code from the stacks there, mind you.)
The use is in
while the free is
I cannot seem to reproduce this trivially.
I'm going to keep poking at this, both from our side and libevent, but I'd be grateful for help. 😄
This is with
master
from github as of last week.(The thread sanitizer seemed to give me a bunch of false positives, although I did change some flags to atomic, and got rid of some bitfields to do the same.)
The text was updated successfully, but these errors were encountered: