right file path

[zdyj3170101136]

problem

the file path is not consistent.

go pprof profile

if using go pprof. then the standard library file path like:

  6871: 0x4f68ee M=1 fmt.Fprint /usr/local/go1.18/go/src/fmt/print.go:232 s=0

parca agent profile

but if the profile file is collect by parca agent, then the standard library file path like :

 404: 0x40d545 M=1 runtime.mallocgc runtime/malloc.go:842 s=0()

expect behaviour

parca agent profile filepath is same with go pprof profile.

the parca agent could get right go version by get godebuginfo from elf file. so i think it is possible to fix it.

It is important for me, because i need correct file path to connect pprof with source code.

[brancz]

Interesting! This is definitely expected to be consistent. I suspect there is a bug in our symbolizer.

cc @kakkoyun

[kakkoyun]

@zdyj3170101136 Thanks for the report.

Could you please elaborate on your binary? Does the binary include DWARF? (Helps us to understand which symbolization strategy is used)

And if it's possible, could you please attach the captured profile?

[zdyj3170101136]

@zdyj3170101136感谢您的报告。

你能详细说明你的二进制文件吗？二进制文件是否包含 DWARF？（帮助我们了解使用了哪种符号化策略）

如果可能的话，能否请您附上捕获的个人资料？

what i see about parca agent profile is in demo.parca.dev.

you can find that the function runtime.goexit's have wrong file name (do not have go version).

here is the profile file:

https://pprof.me/f9a1f0c

[javierhonduco]

@zdyj3170101136 hi! would it be possible to share the source code and/or both pprof profiles, one taken with parca agent and the other one with pprof?

This information should help us understand what can be causing the problems you are seeing. Thanks!