Re: Why can't I access 'kill_something_info' probes?

[Masami Hiramatsu <mhiramat at redhat dot com>]

Om wrote:
>> Seems this function is implicitly inlined. To access parameters of
> How do we know that? What should I look for?

if you make sure that the function is not inlined, you can use .call
suffix;

probe kernel.function("kill_something_info").call { ... }

If the function is inlined, this will report an error.

>> inline functions is still pending problem for systemtap/gcc. But you can
>> try marker to get the inline function parameter information.
>>
>> For your case, I found kill_something_info is just called in sys_kill
>> and always info.si_signo = sig; info.si_errno = 0 in kill_something_info
>> entry. So no necessary to do another probe. just sys_kill is enough.
> Yeah.. I was curious why I could not probe.

Actually, you can probe it but can not trace local variables because
current debuginfo doesn't include those information.

Thank you,

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com