Write perfmap and jitdump files to /tmp by default#88776
Write perfmap and jitdump files to /tmp by default#88776tommcdon merged 1 commit intodotnet:mainfrom
Conversation
Co-authored-by: David Mason <[email protected]>
|
Tagging subscribers to this area: @tommcdon Issue DetailsPerfmaps and Jitdumps is a Linux kernel feature that allows .NET to symbolicate dynamically generated code with perf_events. The perfmap/jitdump files are processed by the the Linux
|
|
All failures are known issues, merging. |
Perfmaps and Jitdumps is a Linux kernel feature that allows .NET to symbolicate dynamically generated code with perf_events. The perfmap/jitdump files are processed by the the Linux
perftool to generate human readable callstacks for CPU traces, for example. The Linux implementation looks for the perfmap/jitdump files in/tmp(please see https://elixir.bootlin.com/linux/v6.4.3/source/tools/perf/util/symbol.c#L1838). The .NET implementation defaults to writing to/tmpbut this can be overridden with the$TMPDIRenvironment variable. This leads to incorrect behavior in environments where$TMPDIRis in use. This code change alters the behavior and will use/tmpregardless of$TMPDIRsettings. There is a minor fix included with this change that correctly sets perfmap location ifDOTNET_PerfMapJitDumpPathis set.