I’d like to do source code line mappings from runtime pc to source code.
I think that could be much easier if each line in the output of cuobjdump/nvdisasm could contains the instruction offset.
Is there any future development plan for this support?
according to the following post, the first column of the cuobjdump/nvdisasm output is the instruction offset in the current kernel. That may solve part of my problem.
I’m writing a tool using sanitizer API which could help me get the PC of the executed instructions, and I’d like to add the source code mapping feature to my tool.
I know ncu has the source code mapping but it is only for when you have done the profiling, and the pc->source code future is not exposed.