diff options
| author | Johannes Doerfert <johannes@jdoerfert.de> | 2024-07-31 11:49:50 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-31 11:49:50 -0700 |
| commit | 9a1013220b668d846e63f241203b80515dee0a03 (patch) | |
| tree | 29beeaeddf1526fd6d2d73616bb2c1ab35727c9a /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp | |
| parent | 33960ce5a8e26baf05521fd7f8be5c5abb6bb0ff (diff) | |
[Offload] Allow to record kernel launch stack traces (#100472)
Similar to (de)allocation traces, we can record kernel launch stack
traces and display them in case of an error. However, the AMD GPU plugin
signal handler, which is invoked on memroy faults, cannot pinpoint the
offending kernel. Insteade print `<NUM>`, set via
`OFFLOAD_TRACK_NUM_KERNEL_LAUNCH_TRACES=<NUM>`, many traces. The
recoding/record uses a ring buffer of fixed size (for now 8).
For `trap` errors, we print the actual kernel name, and trace if
recorded.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions