From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-25879-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 117019 invoked by alias); 19 Feb 2018 06:55:28 -0000
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
Received: (qmail 116985 invoked by uid 48); 19 Feb 2018 06:55:23 -0000
From: "mysecondaccountabc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22847] ARM OABI syscall tracing issues
Date: Mon, 19 Feb 2018 06:55:00 -0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: runtime
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mysecondaccountabc at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-22847-6586-sRz8UAXDW5@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-22847-6586@http.sourceware.org/bugzilla/>
References: <bug-22847-6586@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-q1/txt/msg00052.txt.bz2

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

--- 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=20
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 =3D kprobe.function("sys_connect") ?
{
        @__syscall_gate(@const("__NR_connect"))
        asmlinkage()
        sockfd =3D int_arg(1)
        serv_addr_uaddr =3D pointer_arg(2)
        addrlen =3D uint_arg(3)
}

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