-
Notifications
You must be signed in to change notification settings - Fork 232
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
Building with Valgrind #192
Comments
Are you able to share your application or a minimal test case that demonstrates the problem? This would be easier to investigate with a reproducer. |
I am still trying to create an example that produces true leaks. I am only able to create small examples that produce "still reachable" leaks which are not my concern (I think altho i suppose over time they become one). I will post it though just for completeness. sample_event.proto
memory_leak.cc
|
Friendly ping :) did you guys ever determine how boost was being built with boost context. I think my example is still valid. The bytes are eventually lost. |
Whenever i run my program I have a lot of memory leaks that come from boost -- i know i cause them but it just says boost. I was reading that Boost Context (a dependency) has to be built with valgrind=on as an option and if not this can cause these erroneous errors.. Is there a possibility that something that could be done here. I looked at the BUILD file and I could not find anything. Sorry if this is the wrong place for this!
The text was updated successfully, but these errors were encountered: