Troubleshooting


If the profiler behaves unexpectedly during the profiling session, or the profiling session fails to start, try the following steps:

To enable logging on the host, refer to this config file:

Host-x86_64/nvlog.config.template

When reporting any bugs please include the build version number as described in the HelpAbout dialog. If possible, attach log files and report (.qdrep) files, as they already contain necessary version information.

NVIDIA System Profiler uses a settings file (NVIDIA Tegra System Profiler.ini) on the host to store information about loaded projects, report files, window layout configuration, etc. Location of the settings file is described in the HelpAbout dialog. Deleting the settings file will restore NVIDIA System Profiler to a fresh state, but all projects and reports will disappear from the Project Explorer.

Android Targets

When connecting to an Android-based device, NVIDIA System Profiler installs its executable and library files into the following directory:

/data/local/tmp/com.nvidia.tegraprofiler.tools/

Logs on the target device are collected into this file:

/data/local/tmp/com.nvidia.tegraprofiler.tools/quadd_d.log

To enable verbose logging on the target device, follow these steps:

Please note that in some cases, debug logging can significantly slow down the profiler.

Linux Targets

When connecting to a Linux-based device, NVIDIA System Profiler installs its executable and library files into the following directory:

/opt/nvidia/tegra_system_profiler/

Logs on the target devices are collected into this file:

/var/log/quadd_d.log

To enable verbose logging on the target device, follow these steps:

Please note that in some cases debug logging can significantly slow down the profiler.


 

NVIDIA® System Profiler Documentation Rev. 3.9.170817 ©2017. NVIDIA Corporation. All Rights Reserved.