Daniel Beckwith
Daniel Beckwith
I've found that I can get the kernel to pause on an exception and then I can attach `cuda-gdb` to it, but I still need a PTX file with debug...
Actually, this is pretty easy. I can make a PR.
This is my first go at it as well. Reading the NVIDIA docs it seems pretty straightforward. The best feature I've seen so far is that if you set the...
From playing round a bit, in both release and debug mode, I get linker errors saying it cannot select things like `fpow` and `fcos`, which wasn't happening with `llvm 5.0`....
Also, with a very simple kernel that does compile and link in debug mode, when I try to load it the driver gives me `CUDA_ERROR_INVALID_PTX`. It still works in release...
Thanks, I'll look into using a library to provide the math functions. Would it help if I provided the full PTX causing `CUDA_ERROR_INVALID_PTX`?
https://www.dropbox.com/s/kghoah6wobqcx5a/proxy.ptx?dl=1 I've noticed that the PTX file has names with `.` in them, which you said before was invalid, so maybe that's part of it?
It not longer causes `CUDA_ERROR_INVALID_PTX`, but I think it's just because it's [not building in debug mode](https://github.com/denzp/rust-ptx-builder/blob/master/src/builder.rs#L43).
Ah, never mind, I see that I just have to set it to run in debug mode. I will try that out.
Okay, confirming that my PTX built in debug mode does not cause `CUDA_ERROR_INVALID_PTX` anymore. However, when I try to debug using `cuda-gdb`, it keeps telling me "No symbol table info...