Hi, slowly approaching volatility3 here. Now, that I learned to build dwarf2json¹ (home:frispete:Tumbleweed/ dwarf2json), I've tried to actually use it. $ zyp in kernel-default-debuginfo $ dwarf2json linux --elf /usr/lib/debug/boot/vmlinux-5.8.0-8-default.debug > 5.8.0-8-default.json Failed linux processing: could not get DWARF from /usr/lib/debug/boot/ vmlinux-5.8.0-8-default.debug: decoding dwarf section info at offset 0x2705: underflow Just generating the symbol map lloks fine: $ dwarf2json linux --system-map /boot/System.map-5.8.0-8-default > 5.8.0-8- default-syms.json Q is, who/what to blame here? Is it our infrastructure, that generates DWARF for the kernel in an unusual way, or is it dwarf2json itself? Pete ¹) Already submitted to security:forensics, as well as updates for a couple of related packages: yara, volatility3. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org