[Bug runtime/22847] ARM OABI syscall tracing issues

[mysecondaccountabc at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=22847

--- Comment #6 from Gustavo Moreira <mysecondaccountabc at gmail dot com> ---
I've found the all_syscalls.stp script in the SystemTap's source tree which
show the sys_socket and sys_connect syscalls correctly.

~/systemtap/testsuite/systemtap.syscall# ./all_syscalls.stp -c ~/ex_socket_OABI 
kernel.function("sys_sigreturn_wrapper")?
  kernel.function("sys_sigreturn@arch/arm/kernel/signal.c:189")?
kernel.function("SyS_rt_sigaction@kernel/signal.c:3323")?
kernel.function("SyS_rt_sigprocmask@kernel/signal.c:2543")?
kernel.function("SyS_setitimer@kernel/time/itimer.c:278")?
kernel.function("SyS_execve@fs/exec.c:1906")?
kernel.function("SyS_ioctl@fs/ioctl.c:685")?
kernel.function("SyS_ioctl@fs/ioctl.c:685")?
kernel.function("SyS_socket@net/socket.c:1218")?
kernel.function("sys_oabi_connect@arch/arm/kernel/sys_oabi-compat.c:387")?
  kernel.function("SyS_connect@net/socket.c:1529")?
Connected
kernel.function("SyS_write@fs/read_write.c:599")?
kernel.function("SyS_exit@kernel/exit.c:899")?

However, any of the probe alias are called when for instance sys_connect is
called:

# stap -ve 'probe nd_syscall.*  { printf("%s %s\n", ppfunc(), name) }' -c
./ex_socket_OABI 2>&1 | grep -i connect
Connected

# stap -ve 'probe syscall.*  { printf("%s %s\n", ppfunc(), name) }' -c
./ex_socket_OABI 2>&1 | grep -i connect
Connected

I wonder why the following probe in tapset/linux/sysc_connect.stp doesn't do
the job:
probe __nd_syscall.connect = kprobe.function("sys_connect") ?
{
        @__syscall_gate(@const("__NR_connect"))
        asmlinkage()
        sockfd = int_arg(1)
        serv_addr_uaddr = pointer_arg(2)
        addrlen = uint_arg(3)
}

-- 
You are receiving this mail because:
You are the assignee for the bug.