From: Chris Dunlop <chris@onthe.net.au>
To: Josh Stone <jistone@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, systemtap@sourceware.org
Subject: Re: Can't set statement probe in self-built linux-4.4
Date: Thu, 14 Jul 2016 17:30:00 -0000 [thread overview]
Message-ID: <20160714172954.GB21627@onthe.net.au> (raw)
In-Reply-To: <bae936b3-3675-e463-da84-fbb3cc857ae4@redhat.com>
On Thu, Jul 14, 2016 at 10:20:56AM -0700, Josh Stone wrote:
> On 07/14/2016 09:08 AM, Chris Dunlop wrote:
> > On Fri, Jul 01, 2016 at 01:43:02PM +1000, Chris Dunlop wrote:
> > Any ideas?
>
> $ grep DEBUG_INFO .config
> CONFIG_DEBUG_INFO=y
> # CONFIG_DEBUG_INFO_REDUCED is not set
> CONFIG_DEBUG_INFO_SPLIT=y
> CONFIG_DEBUG_INFO_DWARF4=y
>
> I think SPLIT is the problem. This puts all debuginfo into separate
> .dwo objects, and then vmlinux itself only contains DW_AT_GNU_dwo_name
> references from each CU.
>
> There's no dwo_name support at all in elfutils yet, thus stap doesn't
> support it either.
>
> The function probe that you are getting is based only on the symbol
> table, which is why you're not seeing any arguments either. And
> statement probes aren't available at all without working debuginfo.
OK, that sounds like it explains the problem.
I'll remove the SPLIT and let you know...
Thanks!
Chris
next prev parent reply other threads:[~2016-07-14 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 7:58 Chris Dunlop
2016-06-30 14:58 ` Frank Ch. Eigler
2016-06-30 22:34 ` Chris Dunlop
2016-07-01 16:12 ` David Smith
2016-07-01 20:44 ` Chris Dunlop
[not found] ` <20160701034302.GA23357@onthe.net.au>
2016-07-04 20:55 ` Chris Dunlop
2016-07-14 16:08 ` Chris Dunlop
2016-07-14 16:55 ` David Smith
2016-07-14 17:27 ` Chris Dunlop
2016-07-14 18:23 ` David Smith
2016-07-14 17:21 ` Josh Stone
2016-07-14 17:30 ` Chris Dunlop [this message]
2016-07-14 23:19 ` Chris Dunlop
2016-07-15 13:57 ` David Smith
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=20160714172954.GB21627@onthe.net.au \
--to=chris@onthe.net.au \
--cc=fche@redhat.com \
--cc=jistone@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).