From: Tino Mettler <tino.mettler@tikei.de>
To: elfutils-devel@sourceware.org
Subject: Missing .gnu_debugdata section on ARM platform when libdw is used by systemd-coredump
Date: Tue, 4 May 2021 14:15:41 +0200 [thread overview]
Message-ID: <892EDCB7-C2A8-4497-8FF1-986A63EA7F4A@tikei.de> (raw)
Hi,
I have a system running on 2 different architectures: AMD64 and ARM. When a coredump happens, I want systemd-coredump to generate a stack trace of the crashing application. Systemd depends on elfutils for this feature. I use binaries with minidebuginfo (the LZMA compressed symbol table in the .gnu_debugdata section) on both architectures.
I get a stack trace on AMD64, but not on ARM. While debugging this, I saw that find_aux_sym() from dwfl_module_getdwarf.c does not find a .gnu_debugdata section when iterating through the ELF using elf_nextscn().
However, it finds a .gnu_debuglink section. I inspected the executable and verified that it contains a .gnu_debugdata section and it looks fine. Interestingly, there is no .gnu_debuglink section in the executable despite elf_nextscn() seems to find one.
It looks like libdw does not process the actual executable, but a modified variant, and the .gnu_debugdata section gets lost at some point on my ARM device. Can you give me a hint where I need to look at? Both devices run a different kernel with a different configuration. Could that be related?
I also tried gdb using the coredump file from systemd-coredump and the same executable, and a stack trace worked as expected.
Regards,
Tino
next reply other threads:[~2021-05-04 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 12:15 Tino Mettler [this message]
2021-05-06 0:49 ` Mark Wielaard
2021-05-18 13:33 ` Tino Mettler
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=892EDCB7-C2A8-4497-8FF1-986A63EA7F4A@tikei.de \
--to=tino.mettler@tikei.de \
--cc=elfutils-devel@sourceware.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).