-
Notifications
You must be signed in to change notification settings - Fork 94
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
Segmentation fault when libdds.so is unload #91
Comments
The same script works for me on Ubuntu 18.04. Are you sure you are running with master from my fork of the repository. My fork contains all my fixes and new features. I am not a contributor here - this project has been in silence for a few months now. The stack dump suggests FreeMemory is called from the dll destructor, which I have removed. |
The backtrace mentioned above was generated with the code of the official repository, not yours. But, as I saw you proposed some fixes, I tried to compile
This time, the error was located in the destructor of the Memory class. I made some changes to bypass the problem. You can find what I did in my fork of your work. In my opinion, it's not clean but it works: Python can release the lib without any error. I guess there is a problem because the memory is clean twice (but, to be honest, I don't know the code of this project, so it's just a supposition). |
Thanks! I'll add rimmington's fixes to the next release. |
I experienced the same problem although with a different setup: Following the above suggestions from rimmington I changed two files: Init.cpp and Memory.cpp and recompiled the libdds.so library. Rechecking the above setup did not produce any error. Greetings |
I compiled libdds.so on Linux with the default parameter and I'm trying to use it with ctypes in Python. I noticed, when I unload the library at the end of a Python script, I get a segmentation fault.
Here is a toy example of Python script:
When I run it:
According to the debugger, the issue come from FreeMemory function:
An idea about how to correct that issue?
The text was updated successfully, but these errors were encountered: