This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: process return probes not available with inode-based uprobes
- From: "Turgis, Frederic" <f-turgis at ti dot com>
- To: agentzh <agentzh at gmail dot com>, "systemtap at sourceware dot org" <systemtap at sourceware dot org>
- Date: Thu, 26 Jul 2012 06:39:13 +0000
- Subject: RE: process return probes not available with inode-based uprobes
- References: <CAB4Tn6Mw9h_G1oR01P_4MLWV63rNbvxpAD365u0dmFWfwcTmMw@mail.gmail.com>
My 2cents: this is all in the error message, inode-based process probes do not support (yet ?) return probes, only utrace-based process probes do.
But I don't know the story for future roadmap, how people deal with this...
Regards
Fred
OMAP Platform Business Unit - System Platform Engineering - Platform & Product Entitlement
>
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920
-----Original Message-----
>From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org] On Behalf Of agentzh
>Sent: Thursday, July 26, 2012 6:02 AM
>To: systemtap@sourceware.org
>Subject: process return probes not available with inode-based uprobes
>
>Hello!
>
>I'm trying systemtap 1.8 (from yum) and 2.0-14916 (from git) on Fedora
>17 and I'm getting the following error when trying to specify a
>user-space function return probe:
>
>semantic error: while resolving probe point: identifier 'process' at
>/tmp/QX2q_gw.stp:2:7
> source: probe
>process("nginx").function("ngx_http_lua_process_args_option").return {
>println("Fire ", pp()) }
> ^
>
>semantic error: process return probes not available with inode-based uprobes
>
>Any suggestion to avoid this? Sorry if this question has been asked
>before, but I fail to find an anwser in Google :(
>
>Thanks in advance!
>
>Best regards,
>-agentzh