Hi, and thank you for reaching us out!
Sorry to hear that you’ve experienced some inconvenience while using the product.
The described behavior could mean that the JVM debugger has failed to locate a directory containing Java .class files on the host PC.
This directory is located under the MSBuild project’s intermediate directory $(IntDir)
Try to figure out its path by searching for .class files in the project’s intermediate directory.
For example, for a sample project the class directory is “C:\AndroidApplication\Tegra-Android\Debug\build\intermediates\classes\debug\com\example\app”
One of the class files has the path “C:\AndroidApplication\Tegra-Android\Debug\AndroidApplication\build\intermediates\classes\debug\com\example\app\AndroidApplication.class”
Please add the path of the aforementioned class directory to the project property Java Classes Directories at the Debugging page as demonstrated on the attached screenshot:
Please, make sure that Debug Mode is set to Java and Native code
Also, it helps to check the extension’s log file at %AppData%\Roaming\NVIDIA Corporation\Nsight Tegra\Logs\Nsight Tegra.log
Search for the records like
ClassFileManager|Classes for C:\androidapplication\src\com\example\app\AndroidApplication.java
-launch: C:\Program Files\Java\jdk1.8.0_51\bin\javap.exe "-l -private androidapplication" [c:\androidapplication\tegra-android\debug\build\intermediates\classes\debug\com\example\app]
[JDB] stdout: =class-loaded,reason="com.example.app.AndroidApplication"
I would kindly ask you to upload the aforementioned log file for us to inspect.