From 0325de653802b6453d841d6362f7eeec5248981d Mon Sep 17 00:00:00 2001 From: Pratik Basyal Date: Fri, 7 Nov 2025 18:49:23 -0500 Subject: [PATCH] [ROCm Systems Profiler] Path issue note added to Profiling python script (#1766) * Note added to Profiling python script * Doxygen reverted * Update projects/rocprofiler-systems/docs/how-to/profiling-python-scripts.rst Co-authored-by: David Galiffi --------- Co-authored-by: David Galiffi --- .../docs/how-to/profiling-python-scripts.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/projects/rocprofiler-systems/docs/how-to/profiling-python-scripts.rst b/projects/rocprofiler-systems/docs/how-to/profiling-python-scripts.rst index d25d9ad74f..84c385647e 100644 --- a/projects/rocprofiler-systems/docs/how-to/profiling-python-scripts.rst +++ b/projects/rocprofiler-systems/docs/how-to/profiling-python-scripts.rst @@ -49,6 +49,14 @@ Both the ``share/rocprofiler-systems/setup-env.sh`` script and the module file i ``share/modulefiles/rocprofiler-systems`` automatically handle the prefixing of the ``PYTHONPATH`` environment variable. +.. note:: + + Profiling PyTorch and other AI workloads might fail because it is unable to find the libraries in the default linker path. As a workaround, you need to explicitly add the library path to ``LD_LIBRARY_PATH``. For example, when using PyTorch with Python 3.10, add the following to the environment: + + .. code-block:: shell + + export LD_LIBRARY_PATH=:/opt/venv/lib/python3.10/site-packages/torch/lib:$LD_LIBRARY_PATH + Running ROCm Systems Profiler on a Python script ================================================