fix(cuda.core): let cuda-gdb display source for JIT-compiled kernels - #2678
Open
brandon-b-miller wants to merge 2 commits into
Open
fix(cuda.core): let cuda-gdb display source for JIT-compiled kernels#2678brandon-b-miller wants to merge 2 commits into
brandon-b-miller wants to merge 2 commits into
Conversation
github-actions
Bot
added
the
cuda.core
|
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
1 participant
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.
NVRTC appears to treat the program
namepassed as the path of the source file which it then propagates to the cubins dwarf table. However, Program compiles a string. So there's not actually a file at that path. cuda-gdb needs this to exist to show the source lines.This PR proposes to fix this issue by creating a temporary file when debug is passed that exists for the process lifetime. This fix targets the use case of running the program containing the compilation through a
cuda-gdbsession and not any post-hoc debugging of such a program.Closes #2385