linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milian Wolff <mail@milianw.de>
To: linux-perf-users@vger.kernel.org
Subject: Re: Access to backtraces from user-space tracepoint callback in perf-script?
Date: Wed, 07 May 2014 14:46:31 +0200	[thread overview]
Message-ID: <4531806.6Q1YW4Luy6@milian-kdab2> (raw)
In-Reply-To: <1998748.ORBRrU6aol@milian-kdab2>

On Tuesday 29 April 2014 17:44:54 Milian Wolff wrote:
> Hello,
> 
> today I played around with perf-script(-python) and custom tracepoints. What
> I could not figure out so far is how to print a backtrace from the python
> callback. Can someone explain me how this is done, or point me to the
> documentation for this?

Ping? Could someone help me here please?
-- 
Milian Wolff
mail@milianw.de
http://milianw.de

  reply	other threads:[~2014-05-07 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 15:44 Access to backtraces from user-space tracepoint callback in perf-script? Milian Wolff
2014-05-07 12:46 ` Milian Wolff [this message]
2014-05-14  0:33   ` Namhyung Kim
2014-05-14  8:47     ` Milian Wolff
2014-05-16 15:57       ` Frank Ch. Eigler
2014-05-17 11:24         ` Milian Wolff
2014-05-17 14:31           ` David Ahern

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=4531806.6Q1YW4Luy6@milian-kdab2 \
    --to=mail@milianw.de \
    --cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).