stap --dyninst with C++ applications

stap --dyninst with C++ applications

[Siva N]

Hi,

I am curious to understand how C++ object arguments are handled with USDT.

I have a C++ application. I have added probe points using the DTRACE_PROBE[n] macro. If I pass a reference/pointer to a C++ object as one of the arguments, I wonder how one accesses this inside the probe handler. I could treat the argument(s) as a void pointer, and if I managed create the actual C++ object layout, I guess I could access the data. But I was wondering if there were any other suggestions or examples.

Thanks!

Re: stap --dyninst with C++ applications

[Stan Cox]

> I am curious to understand how C++ object arguments are handled with USDT.
> 
> I have a C++ application. I have added probe points using the DTRACE_PROBE[n] macro. If I pass a reference/pointer to a C++ object as one of the arguments, I wonder how one accesses this inside the probe handler. I could treat the argument(s) as a void pointer, and if I managed create the actual C++ object layout

--dyninst should handle probe("NAME").mark("LABEL") probes fine.  If I 
have the small c++ sample:

> #include <string>
> #include <iostream>
> #include <tstclass.h>
> using namespace std;
> 
> struct A
> {
>   A();
>   long aa;
>   long bb;
>   string string1;
>   string string2;
> };
> 
> A::A ()
> {
>   aa = 10;
>   bb = 20;
>   string1 = "abc";
>   string2 = "xyz";
> }
> 
> int main()
> {
>   struct A anA;
>   SDT_MISC_TEST_PROBE_4(&anA);
>   std::cout << anA.aa << ' ' << anA.bb << ' ' << anA.string1 << ' ' << anA.string2 << ' ' << '\n';
> }

and the .d file:
> provider sdt_misc {
> 	probe test_probe_4 (struct A arg);
> };

Then the arg struct corresponding to SDT_MISC_TEST_PROBE_4 can be 
accessed via:
> function get_string:string (str)
> %{
>   char astr[32];
>   strcpy (astr,(char*)STAP_ARG_str);
>   STAP_RETURN (astr);
> %}
> 
> probe process("./tstclass.x").mark("test_probe_4") 
> { 
>   printf("%s aa=%#lx string1=%s\n",pp(),@cast($arg1,"struct A")->aa, 
> 	 get_string(@cast($arg1,"struct A")->string1->_M_dataplus->_M_p))
> }

The @cast interprets arg1 as a struct A so the members can be accessed. 
  The probes are translated to C so it uses internal knowledge to get at 
string1.  (Is there an easier way to do this?)  So that yields:
% stap --dyninst -g --disable-cache tstclass.stp -c ./tstclass.x
process("/this/dir/tstclass.x").statement(0x401283) aa=0xa string1=abc
10 20 abc xyz