GTest tries to run the *.o file Cuda CLion debug
I have recently changed the CMake file for the project to allow for separate compile for Cuda to allow dynamic parallelism.
Everything builds fine but will trying to run any test, not just Cuda related code, Clion tries to run the cmake.device.o file.
I just need to ideas of where to start looking to fix the problem. Unless someone knows exactly what to do, which would be great.
Here's the output.
Testing started at 6:59 AM ...
/home/developer/Source/selene_build/src/selene/CMakeFiles/gpu_image_test.dir/cmake_device_link.o --gtest_filter=GpuImage.CalculateGradient:GpuImage/*.CalculateGradient:*/GpuImage.CalculateGradient/*:*/GpuImage/*.CalculateGradient --gtest_color=no
/bin/sh: 1: exec: /home/developer/Source/selene_build/src/selene/CMakeFiles/gpu_image_test.dir/cmake_device_link.o: Permission denied
During startup program exited with code 126.
Process finished with exit code 0
Empty test suite.
请先登录再写评论。
Hello! Sorry for the inconvenience. We have a related issue in our tracker: https://youtrack.jetbrains.com/issue/CPP-10292. Please comment or upvote in order to get updates.
As a workaroud you can create a new target with the actual executable file. Also there is a CLion CUDA Run Patcher plugin created by one of our users.
I tried the plugin on CLion 2018.1.3 and it does not work.
Can you provide some steps to what you mean about adding a new target?
Thank you for your quick response.
You can manually add a run/debug configuration using the same target and manually setting the executable ("Select other..." in the drop-down menu). Please see the comments in https://youtrack.jetbrains.com/issue/CPP-10292.
Hey Anna!
Thanks for the help yesterday, just a little feedback.
The work around is good and I can use break points. But unfortunately, I can't run individual tests.
Also, I installed the latest version of CLion yesterday and the bug is still present in that version.
The plug-in doesn't work for me. I think its because I use out of source builds, not the default location
cmake-build-[configuration].Should I update issue CPP-10292 with these comments?
thanks
Jason,
Thanks for the details.
>Also, I installed the latest version of CLion yesterday and the bug is still present in that version.
https://youtrack.jetbrains.com/issue/CPP-10292 still has the "Open" state. It will get the "Fixed" stated when we fix the issue. The CLion version with the fix will appear in the "Fix versions" state.
>The plug-in doesn't work for me. I think its because I use out of source builds, not the default location
cmake-build-[configuration].Since it's a third-party plugin, please leave your comments in its issue tracker: https://github.com/anantapalani/clion-cuda-run-patcher/issues.