From: Mark Wielaard <mark@klomp.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
systemtap@sourceware.org
Subject: Re: perf probe line numbers + CONFIG_DEBUG_INFO_SPLIT=y
Date: Wed, 18 Apr 2018 16:19:57 +0200 [thread overview]
Message-ID: <1524061197.17523.10.camel@klomp.org> (raw)
In-Reply-To: <20180418230301.fd26676ece5b2dc16d98b266@kernel.org>
On Wed, 2018-04-18 at 23:03 +0900, Masami Hiramatsu wrote:
> It shows where we can see the .dwo file.
> However, it seems elfutils doesn't support dwo.
>
> $ eu-readelf --debug-dump=info ~/kbin/linux.x86_64/fs/namei.dwo
> eu-readelf: cannot get debug context descriptor: No DWARF information
> found
>
> As above gcc article said, the section name has been changed.
>
> $ eu-readelf -S ~/kbin/linux.x86_64/fs/namei.dwo There are 10 section
> headers, starting at offset 0x49440:
>
> Section Headers:
> [Nr]
> Name Type Addr Off Size
> ES Flags Lk Inf Al
> [ 0] NULL 0000000000000000 00000000
> 00000000 0 0 0 0
> [ 1] .debug_info.dwo PROGBITS 0000000000000000 00000040
> 000252d7 0 E 0 0 1
> [ 2] .debug_abbrev.dwo PROGBITS 0000000000000000 00025317
> 00000f2f 0 E 0 0 1
> [ 3] .debug_loc.dwo PROGBITS 0000000000000000 00026246
> 00004f9b 0 E 0 0 1
>
>
> And I found below description in systemtap
> document(man/error::dwarf.7stap).
> ===
> debuginfo configuration
> Some tools may generate debuginfo that is unsupported by systemtap,
> such
> as the linux kernel CONFIG_DEBUG_INFO_SPLIT (\f2.dwo\f1 files)
> option.
> Stick with plain ELF/DWARF (optinally split, Fedora-style), if
> possible.
> ===
>
> So, it seems that elfutils may not support this split debuginfo yet.
No, it doesn't yet. I am working on it. Work in progress patches here:
https://code.wildebeest.org/git/user/mjw/elfutils/log/?h=dwarf5
That includes work on DWARF5 (which also supports split DWARF, but
slightly different from how GNU DebugFission works...).
I am trying to keep the interface of libdw completely the same. In most
cases things should work as is, even though the DIEs or locations come
from different sections/files. But have added some new functions to
"jump" from the skeleton DIEs to split DIEs in case the user needs to
know about the difference (and you probably want to, because otherwise
it will look like you just get "empty" skeleton DIE trees - see the
patches for eu-readelf --debug-dump=info+ and --dwarf-skeleton - but
those are very much WIP, don't use them as is, they are more to
figuring out what interfaces we need).
elfutils 0.171 with support for DWARF5, split DWARF and those new
interfaces should be out as soon as those WIP patches have been cleaned
up.
Once that is done, I'll use the new interfaces to add support to
systemtap.
Cheers,
Mark
next prev parent reply other threads:[~2018-04-18 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 17:47 perf probe line numbers + CONFIG_DEBUG_INFO_SPLIT=y Arnaldo Carvalho de Melo
2018-04-18 3:23 ` Masami Hiramatsu
2018-04-18 14:03 ` Masami Hiramatsu
2018-04-18 14:19 ` Mark Wielaard [this message]
2018-04-18 15:05 ` 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=1524061197.17523.10.camel@klomp.org \
--to=mark@klomp.org \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=systemtap@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