All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: david lerner <dlernerdroid@gmail.com>
Cc: linux-perf-users@vger.kernel.org,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: perf probe dwarf on shared libraries
Date: Thu, 11 Sep 2014 11:51:19 -0300	[thread overview]
Message-ID: <20140911145119.GG10158@kernel.org> (raw)
In-Reply-To: <CANq2XvGNtBO2zVoGTZJkfUofRbZ94-NJ5hZrSz5BT3En4dEHJA@mail.gmail.com>

Em Thu, Sep 04, 2014 at 03:11:31PM -0500, david lerner escreveu:
> Has perf probe for userspace shared libraries been modified to use dwarf info?
> The first commit to provide this useful functionality...
>    fb7345bbf7fad9  perf probe: Support basic dwarf-based operations on
> uprobe events,
> shows examples only with the executable perf, but not with a shared library.
 
> With version 3.14 I'm able to set probes in application executable,
> for example for the test application 'libunwind-test.out' I see the
> usual args to main():
>    root@qemu0:~# perf probe -x ./libunwind-test.out --vars main
>    Available variables at main
>         @<main+0>
>                 char**  a
>                 int     c
> But I can't access the variables in a library that has embedded (not
> split out) dwarf debug info...
>    root@qemu0:~# perf probe -x /usr/lib64/libunwind.so --vars unw_backtrace
>    Failed to find symbol at 0x33c38039cd
>    Failed to find variables at unw_backtrace (-2)
>    Error: Failed to show vars. (-2)
> I've used gdb to confirm that perf found the correct function address
> for unw_backtrace(), and that gdb knows the symbolic names of the
> arguments.
 
> Is using dwarf debuginfo with shared libraries for perf uprobes on the
> to-do list?
> Or is this capability incomplete in version 3.14 and I need to pick up
> other patches?

Have to check this, but perhaps Masami has this working already?

- Arnaldo

  reply	other threads:[~2014-09-11 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 20:11 perf probe dwarf on shared libraries david lerner
2014-09-11 14:51 ` Arnaldo Carvalho de Melo [this message]
2014-09-12  2:57   ` Masami Hiramatsu

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=20140911145119.GG10158@kernel.org \
    --to=acme@kernel.org \
    --cc=dlernerdroid@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.