From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
systemtap@sourceware.org, Mark Wielaard <mark@klomp.org>
Subject: Re: perf probe line numbers + CONFIG_DEBUG_INFO_SPLIT=y
Date: Wed, 18 Apr 2018 12:05:16 -0300 [thread overview]
Message-ID: <20180418150516.GB10084@kernel.org> (raw)
In-Reply-To: <20180418230301.fd26676ece5b2dc16d98b266@kernel.org>
Em Wed, Apr 18, 2018 at 11:03:01PM +0900, Masami Hiramatsu escreveu:
> 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.
Ok, what about detecting that this is the case: .dwo is being used, as
detected by the presence of those .debug_*.dwo ELF sections and then
warning the user that this mode of operation is not supported yet?
- Arnaldo
prev parent reply other threads:[~2018-04-18 15:05 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
2018-04-18 15:05 ` Arnaldo Carvalho de Melo [this message]
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=20180418150516.GB10084@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@klomp.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