Re: How do I trap the return of a function in a user space process?

[Martin Martin <martin at infinio dot com>]

I manged to solve this problem: I was compiling with clang++.
Switching to g++ caused all my functions to show up.

Thanks,
Martin

On Fri, Sep 6, 2013 at 11:57 AM, Martin Martin <martin@infinio.com> wrote:
> My next problem is that all of the C++ methods in the class I'm
> interested in don't show up when I do:
>
> sudo stap -l 'process("myexe").function("*")'
>
> Although static methods defined in the same .cpp file do show up.  The
> mangled names don't show up in the output of .function("_Z*"),
> although nm shows them just fine.  How does systemtap decide what to
> filter out and what to keep?
>
> Thanks again,
> Martin
>
>
> On Fri, Sep 6, 2013 at 10:17 AM, Martin Martin <martin@infinio.com> wrote:
>> Hi,
>>
>> Thanks a lot for your response.  I created a virtual machine running
>> the latest beta of Ubuntu 13.10, which is Linux 3.11.0, and I can now
>> probe returns!
>>
>> However, I only get events (function enter or exit) if I start the
>> process from stap using -c.  If I just run the process from the shell,
>> then run stap, I don't get any events. Any idea what I could be doing
>> wrong?
>>
>> Thanks,
>> Martin
>>
>> On Thu, Sep 5, 2013 at 4:42 PM, Yichun Zhang (agentzh)
>> <agentzh@gmail.com> wrote:
>>> Hello!
>>>
>>> On Thu, Sep 5, 2013 at 1:36 PM, Martin Martin wrote:
>>>> The following systemtap script fails to compile:
>>>>
>>>> probe process("myexe").function("myFun").return { print("hi mom\n") }
>>>>
>>> [...]
>>>>
>>>> I'm on Ubuntu 13.04, Linux 3.8.0-29-generic, system tap 2.1/0.153.
>>>>
>>>
>>> The Linux kernel 3.8 does not support uretprobes. I think you need to
>>> use kernel 3.10+ for that or downgrade to older kernels with the
>>> utrace patch applied.
>>>
>>> Regards,
>>> -agentzh