Hello Nvidia! I am testing profiling the sample code Vectoradd.cu in the cuda-sample master from a RTX4060-laptop GPU. Here is the Error report
ApplicationExitedBeforeProfilingStarted (1104) {
RuntimeError (120) {
OriginalExceptionClass: struct boost::wrapexcept
OriginalFile: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Host\Analysis\Clients\AnalysisHelper\AnalysisStatus.cpp
OriginalLine: 81
OriginalFunction: class Nvidia::QuadD::Analysis::Data::AnalysisStatusInfo __cdecl QuadDAnalysis::AnalysisHelper::AnalysisStatus::MakeFromErrorString(enum Nvidia::QuadD::Analysis::Data::AnalysisStatus,enum Nvidia::QuadD::Analysis::Data::AnalysisErrorType::Type,const class std::basic_string<char,struct std::char_traits,class std::allocator > &,const class boost::intrusive_ptr &)
ErrorText: The target application exited before profiling started.
}
Could there be any help or error log to be needed? Thanks!
I’m not sure what your exact command line was, but from the look of it, the code actually ran so quickly that the profiler did not have time to collect any meaningful data.
Actually,I tested the simple_stream example, and trying a longer repitition up to 10000 instead of 100 in the original example, the output of the program is
and the first line of the nvlog is shown as.
during the
while eventually the out put of the profiling process is the same
.
and the error goes as.
ApplicationExitedBeforeProfilingStarted (1104) {
RuntimeError (120) {
OriginalExceptionClass: struct boost::wrapexcept
OriginalFile: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Host\Analysis\Clients\AnalysisHelper\AnalysisStatus.cpp
OriginalLine: 81
OriginalFunction: class Nvidia::QuadD::Analysis::Data::AnalysisStatusInfo __cdecl QuadDAnalysis::AnalysisHelper::AnalysisStatus::MakeFromErrorString(enum Nvidia::QuadD::Analysis::Data::AnalysisStatus,enum Nvidia::QuadD::Analysis::Data::AnalysisErrorType::Type,const class std::basic_string<char,struct std::char_traits,class std::allocator > &,const class boost::intrusive_ptr &)
ErrorText: The target application exited before profiling started.
}
}
the full log file is here.
nsys-ui.log (8.8 MB)
Maybe there is some command line argument that is not inserted? Here is my setting
Looking forward to your reply, thanks!
The options look correct and solid to me. I’m more of an expert on the linux target though, so I am going to ask @dofek to assign someone to take a look at this.
Hi,
I confirm this is a bug in Nsight Systems.
To overcome the issue, either:
- Uncheck the hotkey checkbox to let profiling begin automatically when the you click the Start button.
- Or, keep the hotkey checkbox checked, and check the “Start profiling manually” checkbox too. Note however that the hotkey option is designed for graphics programs that create a graphics window and should not be used with terminal-based applications.