How to use debuginfod to retrieve symbols on FreeBSD?

Maxnix

Maxnix

Hello all.

Some background first: I noticed an abnormal memory usage by plasmashell, and discovered that the problem is not strictly related to Plasma on FreeBSD how demonstrates the following thread on KDE discuss: https://discuss.kde.org/t/high-memory-usage-from-plasmashell-is-it-a-memory-leak/29105.
So I used devel/heaptrack to gather infos and reported to the said discussion, but how meven pointed out, I missed some debugging symbols to make those informations useful, and suggested me to use debuginfod to retrieve the said symbols; and here is where I am lost: I tried to look up how to use debuginfod on FreeBSD but didn't find anything meaningful (or that I'm able to make use of).

So I'm here asking if someone could guide me in using debuginfod to download debug symbols on FreeBSD.

Thank you in advance.
 
Which debug symbols are you looking for? Packages are generally built with their debug symbols stripped off.
 
I don't know which debug symbols are needed in particular, IIUC heaptrack/gdb would have take care of downloading what was needed with debuginfod correctly configured.

If can be useful, here are the links to the log files from heaptrack and a cumulative screenshot from the three files:
heaptrack.plasmashell.5034.zst
heaptrack.plasmashell.46609.zst
heaptrack.plasmashell.97300.zst
fe9bffa7216bd0cba24aeb3e8b2642ffcba2f635.png
 
"Debugging symbols" can mean two things:
  • The names of functions associated with their locations
  • The source code in debugging format

Heaptrack prints backtraces, which only requires the former.

The catch is that some functions might be omitted from this due to omitting frame pointers at optimizations greater than -O1. You want -fno-omit-frame-pointer as a compilation flag for everything. FreeBSD doesn't do that by default. (sadly)

You probably want to debug this problem in a newish Ubuntu or Mint, as they have this flag set for most packages.
 
cracauer@ said:
You probably want to debug this problem in a newish Ubuntu or Mint, as they have this flag set for most packages.
Click to expand...
The problem is that while this leak is not exclusive of FreeBSD, it isn't present on every distro; IIRC Arch was not affected, in example.
I'll try with Kubuntu, let's see what happens. :)
 
You must log in or register to reply here.
Back
Top