Skip to content
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

Investigate where readlink() is coming from when Python is launched on cori. #17

Closed
mcfadden8 opened this issue May 22, 2018 · 1 comment

Comments

@mcfadden8
Copy link
Contributor

No description provided.

@mplegendre
Copy link
Member

@mcfadden8 and I discovered the readlinks of /proc/self/exe are coming from the dynamic linker when the binary contains an $ORIGIN rpath. We're failing to intercept and correct these because they're a direct syscall rather than through libc's readlink. The result of this is that $ORIGIN is expanded to Spindle's cache location where we stashed the executable, and the applications library search path is wrong.

Am closing this "to investigate" issue. It's fixed by running Spindle with "--debug=yes", and we'll use issue #16 to look into making "--debug=yes" default behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants