-
Notifications
You must be signed in to change notification settings - Fork 186
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
PyCall use-after free #33
Comments
Here are the interesting bits immediately le leading up to the segfault:
|
I pass lots of pointers to Python, but I try to be careful to pass pointers only to I suspect that I'm forgetting to increment a reference count somewhere, probably in the new IO code or the |
The use after free thing turns out to be normal and python just hopes it's ok. Here's the relevant part with python debug symbols. You should be able to figure out what object is missing the reference count from where it's deallocated:
|
Relating to the problem we had yesterday. Running
under valgrind gives https://gist.github.com/loladiro/6134837 which has a bunch of instances of use-after-free even those that weren't allocated by Pycall. Are you at any point (in the I/O code perhaps) passing raw pointers to python?
The text was updated successfully, but these errors were encountered: