From: Bitweasil <bitweasil@cryptohaze.com>
To: dwarves@vger.kernel.org
Subject: Ubuntu kernels and die__process: DW_TAG ... got INVALID!
Date: Tue, 4 Oct 2022 15:10:06 -0600 [thread overview]
Message-ID: <17a34291-e28c-b08d-cfec-d455c72c4c54@cryptohaze.com> (raw)
When trying to extract the layout of kernel structures that should exist
on recent kernels from the Ubuntu debug kernel repo, I get the following
error:
die__process: DW_TAG_compile_unit, DW_TAG_type_unit or
DW_TAG_partial_unit expected got INVALID!
pahole: type 'mount' not found
As far as I can tell, 'struct mount' should still exist - and I can pull
other structures out without trouble. The issue starts appearing
somewhere in the 5.15 kernel version - earlier kernels work exactly as
expected and I can extract the full offsets.
https://elixir.bootlin.com/linux/v5.15.48/source/fs/mount.h indicates
that 'struct mount' still exists in the source, and it remains present
into the 6.0 kernel with no substantial changes. I can also produce the
same response with some of the other structures in that file -
mountpoint, mnt_namespace, and mnt_pcp all lead to the same error message.
I've tried building pahole from head (Oct 4, 2022, e819d737) without any
changes to the behavior, and v1.21 and 1.24 both lead to the same results.
Steps to reproduce (warning, will take ~10GB - the unzipped kernel debug
symbols are rather large):
cd /tmp
wget
http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-unsigned-5.15.0-48-generic-dbgsym_5.15.0-48.54_amd64.ddeb
ar x linux-image-unsigned-5.15.0-48-generic-dbgsym_5.15.0-48.54_amd64.ddeb
tar -xf data.tar.xz
cd usr/lib/debug/boot
pahole -C mount vmlinux-5.15.0-48-generic
die__process: DW_TAG_compile_unit, DW_TAG_type_unit or
DW_TAG_partial_unit expected got INVALID!
pahole: type 'mount' not found
Any suggestions on how to resolve this? I'm not familiar enough with
the various debug formats to know how to troubleshoot beyond this point
right now.
next reply other threads:[~2022-10-04 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 21:10 Bitweasil [this message]
2022-10-05 12:20 ` Ubuntu kernels and die__process: DW_TAG ... got INVALID! Arnaldo Carvalho de Melo
2022-10-05 16:59 ` Bitweasil
2022-10-05 18:31 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17a34291-e28c-b08d-cfec-d455c72c4c54@cryptohaze.com \
--to=bitweasil@cryptohaze.com \
--cc=dwarves@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).