-
Notifications
You must be signed in to change notification settings - Fork 62
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
libmercury_util.so.4 causes a segfault on exit when leveraged through Python/CFFI #729
Comments
thanks for reporting the issue, I was able to reproduce it, this seems specific to having mercury compiled with support for dynamic plugins (which is the default for mercury rpms). Looking into a fix now. |
NA: fix missing free of dynamic plugin entries
fix was merged, I'll propagate the fix into the mercury-2.3.1-3 rpm as well. |
Thanks! Much appreciated. |
Was this fix ever propagated into mercury-2.3.1-3? If yes, where are those RPMs available? |
it was internally but I'm not sure you'll be able to see it until a new release of DAOS is made because of the SDL process. Which repo are you using for your rpms ? |
That's a great question. Let me chase this internally and see what I can figure out. Thanks! |
Describe the bug
When using Python and CFFI to dlopen any library that has a dependency on
libmercury.so.2
, a segfault occurs when Python exits, pointing tolibmercury_util.so.4
.To Reproduce
zypper install python3-cffi
zypper install mercury mercury-devel
Expected behavior
No segfault occurs when Python is unloaded.
Platform:
Additional context
The stack trace of
python3
at the time of the segfault as reported by coredumpctl is:The text was updated successfully, but these errors were encountered: