-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Broken backward compatibility with Juliacall #53363
Comments
Can you post the actual backtrace you are seeing? |
I cannot reproduce this on asahi linux
|
Here is what I get when I try to reproduce the error:
I have been able to reproduce it also on a Ubuntu VM.
|
This feels similar to JuliaPy/PythonCall.jl#215, but you have a clean environment, so it shouldn't be a pytorch-julia incompatibility. |
@gbaraldi and I have run into a similar issue upon loading // test.c
#include <stdio.h>
extern char **environ;
__attribute__((constructor))
static void my_init() {
printf("%p \n", environ[0]); // libgomp expects that `environ` has been initialized by libc
} # test.py
import ctypes, os
lib = ctypes.CDLL("./libtest.so", os.RTLD_DEEPBIND) # loading Julia-provided libgomp also segfaults
The problem is that the $ readelf -sW /usr/bin/python3 | grep environ
1622: 0000000000a92620 8 OBJECT WEAK DEFAULT 29 environ@GLIBC_2.2.5 (2)
1700: 0000000000a92620 8 OBJECT GLOBAL DEFAULT 29 __environ@GLIBC_2.2.5 (2)
$ readelf -sW /usr/lib/x86_64-linux-gnu/libc.so.6 | grep environ
133: 0000000000222200 8 OBJECT WEAK DEFAULT 35 _environ@@GLIBC_2.2.5
724: 0000000000222200 8 OBJECT GLOBAL DEFAULT 35 __environ@@GLIBC_2.2.5
958: 0000000000222200 8 OBJECT WEAK DEFAULT 35 environ@@GLIBC_2.2.5 This wasn't an issue before 1.10.1 because |
Resolves JuliaLang#53363 (cherry picked from commit 5c7d244)
The new version 1.10.1 release broke the package juliacall on Linux systems.
When importing the package from python a segmentation fault occurs.
How to reproduce:
pip install juliacall
import juliacall
Note: this does not happen with version 1.10.0 and on Mac devices.
The text was updated successfully, but these errors were encountered: