gh-156703: Set LD_LIBRARY_PATH in SystemTap trace commands - #156424
Conversation
|
cc @encukou this should be fixing the buildbots dtrace issues, however if you can add the label to test with buildbots. |
|
If that works, it also requires the backport to 3.15 label. |
|
🤖 New build scheduled with the buildbot fleet by @StanFromIreland for commit 96277bb 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F156424%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
|
Unfortunately PPC64LE still fails: |
|
Is there a reason to go through |
Us that a failure? That is expected as the dtrace path is not exercised on Linux, Systemtap doesn't have the -q option. |
staprun removes LD_LIBRARY_PATH before starting Python so passing it to Popen is not enough, it must be added to the command that starts Python. |
Prefix commands passed to stap -c with LD_LIBRARY_PATH via env, when probes reside in libpython. This allows the interpreter to find libpython when staprun does not preserve the loader path.
96277bb to
ee07f6f
Compare
|
Rebased to change the commit message to reference the proper issue, no code changes. |
|
Thanks @stratakis for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.15. |
|
GH-156755 is a backport of this pull request to the 3.15 branch. |
|
Thank you! Let's get it in to fix aarch!
No, sorry; pasted a wrong part of the log. |
Prefix commands passed to stap -c with LD_LIBRARY_PATH via env, when probes reside in libpython. This allows the interpreter to find libpython when staprun does not preserve the loader path.