Prevent SEGFAULT when stub-library is being accessed#89
Merged
Conversation
Collaborator
|
Thank you! Did not test in detail but the change seems sound. Do you think this should be a point release, or can we wait until more patches are in? |
Contributor
Author
|
No worries on an urgent release. My use-case involves building with nix so it's easy to pull in an upstream change at an exact commit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Sometimes the
libcuda.soliving in the cudatoolkit'slib/stubs/directory will get intentionally or unintentionally linked into a program in place of the real user-space driver. If this occurs, any calls to this Haskell library will cause a SEGFAULT oncuGetErrorString, which wrongly gives the impression that this library is simply broken and doesn't instruct users where to actually look to fix their issue.