On Thu, 28 Aug 2025 17:27:37 -0300 Arnaldo Carvalho de Melo <arnaldo.melo@xxxxxxxxx> wrote: > >I would love to have a hash to use. The next patch does the mapping > >of the inode numbers to their path name. It can > > The path name is a nice to have detail, but a content based hash is > what we want, no? > > Tracing/profiling has to be about contents of files later used for > analysis, and filenames provide no guarantee about that. I could add the build id to the inode_cache as well (which I'll rename to file_cache). Thus, the user stack trace will just have the offset and a hash value that will be match the output of the file_cache event which will have the path name and a build id (if one exists). Would that work? -- Steve
