Avoid using fork() when probing system libstdc++
#60254
Open
+4,971
−109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Somewhat of a companion to #60248.
For a small application that has just started up
fork()is not a huge concern, but it's quite heavy-handed for Julia- as-a-library scenarios where resident memory may already be large. Many soft-embedded targets also do not support fork() well, so it is good for our compatibility to adjust this.Rather than relying on the linker to do all of the heavy lifting, this changes our
libstdcxxprobe sequence to directly parse theld.so.cacheandlibstdc++.so.6files. As long as we can expect/etc/ld.so.cacheto be the same path on all Linux systems, this seems to be a reliable way to locate system libraries.