Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

Frank Ch Eigler writes: > Hi, Lluís - >> I've attached both. BTW, I'm using debian's gcc 6.1.1-1. > Thank you. Those both look just fine, argh. Could you try using > gdb's "static probe points" facility to break at the same point, to > see if the arguments are accessible? >

Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

Hi, Lluís - > I've attached both. BTW, I'm using debian's gcc 6.1.1-1. Thank you. Those both look just fine, argh. Could you try using gdb's "static probe points" facility to break at the same point, to see if the arguments are accessible?

Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

Frank Ch Eigler writes: > Hi - >> $ cat >test.c <<\EOF >> [...] >> int f(int a1, int a2) >> { >> TEST_F(a1, a2); >> [...] >> } >> >> int main(int argc, char *argv[]) >> { >> f(1, 1); >> f(2, 2); >> return 0; >> } >> EOF >> [...] >> $ gcc -o test -O0 -g test.c events.o >> $ sudo stap test.stp -c

Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

Vincent Bernat writes: > ❦ 13 septembre 2016 19:10 CEST, Lluís Vilanova  : >> Hi! I've been writing some very simple systemtap scripts, and printing the >> values of arguments to user-defined probe marks always shows zeroes. >> >> Here's an minimal failing example: >> >> $

Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

Hi - > $ cat >test.c <<\EOF > [...] > int f(int a1, int a2) > { > TEST_F(a1, a2); > [...] > } > > int main(int argc, char *argv[]) > { > f(1, 1); > f(2, 2); > return 0; > } > EOF > [...] > $ gcc -o test -O0 -g test.c events.o > $ sudo stap test.stp -c './test' > [...] > 0 0 > 0 0

Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

❦ 13 septembre 2016 19:10 CEST, Lluís Vilanova  : > Hi! I've been writing some very simple systemtap scripts, and printing the > values of arguments to user-defined probe marks always shows zeroes. > > Here's an minimal failing example: > > $ cat >events.d <<\EOF > provider

Bug#837697: systemtap: Arguments of user probes are always (incorrectly) zero

Package: systemtap Version: 3.0-6 Severity: normal Hi! I've been writing some very simple systemtap scripts, and printing the values of arguments to user-defined probe marks always shows zeroes. Here's an minimal failing example: $ cat >events.d <<\EOF provider test { probe f(int a1, int