I am trying to profile a CUDA code that is embedded in a mex file, called from MATLAB. Running on a win7 x64 machine, MATLAB r2014b
The code is structured as follows:
MATLAB test.m
->contains some standard code generating variables (and calling 1 or 2 minor own MATLAB fucntions)
-> calls testcuda.mex
->contains small, standard, no library C++ code
-> calls either test1.cu or test2.cu
->.cu files end in cudaDeviceReset();
I did the following, as stated in several places on the internet:
exit
in the end of test.m. C:\\Program Files\\MATLAB\\R2014b\\bin\\matlab.exe
C:\\CUDA_MATLABtests\\MyToolbox
-nojvm -nosplash -r test
However, when I run the profiler,I get
======== Warning: No CUDA application was profiled, exiting
And nothing more.
I am missing some instruction?
Is there any particular code structure that would make the profiler not to profile?
A Matlab installation comes with two binaries, a launcher in <matlabroot>\\bin
and the main application in <matlabroot>\\bin\\<arch>
. The later is the executable which also executes the mex functions in it's address space.
<matlabroot>\\bin\\<arch>
. <matlabroot>\\bin
setting the -wait
parameter. Seeing the launcher application terminating, debugging tools often stop. Never use the binary in <matlabroot>\\bin\\<arch>
directly unless you have to.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.