https://sourceware.org/bugzilla/show_bug.cgi?id=34030
--- Comment #5 from Marek Pazúr <marekpazur1 at seznam dot cz> --- (In reply to Mark Wielaard from comment #3) > (For me they seem to act the same, showing errors for .note.gnu.property, > .note.gnu.build-id and .rodata.) With Total CUs: 0 It is interesting that you are not getting any CUs at all. In my setup I get at least the kernel CUs (around 3100). It is possible I am doing something wrong in how I provide the kernel/module debuginfo. > Which distro are you using? Which kernel (version)? I am currently running Ubuntu 24.04.4 LTS with kernel 6.8.0-111-generic. I installed the debug symbols for the kernel and modules using package manager: `sudo apt install linux-image-$(uname -r)-dbgsym` If I understand correctly, libdwfl either expects the debuginfo to be present in the /lib/modules modules themselves, or in /usr/lib/debug/lib/modules with the modules decompressed, since the .gnu_debuglink sections of the original modules refer to *.ko files. I tried both approaches, first replacing the original module files, and then just decompressing the debug ones in /usr/lib/debug. > Could you show what the output is for you? To keep the output small, I used only the bridge, llc, stp, and xt_nat debug modules for this test. Here is the output I get. Without the wrapper, it stops at the first missing __versions section. With the wrapper, it continues and finds CUs for the affected modules: ``` $ sudo ./test === Without wrapper === kernel debug-info found! (Section __versions error for xt_nat) Total CUs: 3107 === With wrapper === kernel debug-info found! (Section __versions skipped for xt_nat) xt_nat debug-info found! (Section __versions skipped for bridge) bridge debug-info found! (Section __versions skipped for stp) stp debug-info found! (Section __versions skipped for llc) llc debug-info found! Total CUs: 3146 ``` > And maybe make the wrapper also log which secnames show errors? The modified wrapper, doesn't print any errors for me, except the missing __versions section. I also attached a file with more detailed output, where the log/wrapper prints each processed section. This was tested again only with the xt_nat, bridge, stp, and llc debug modules. -- You are receiving this mail because: You are on the CC list for the bug.
