public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-22847-6586-sRz8UAXDW5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22847-6586@http.sourceware.org/bugzilla/>

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.

  parent reply	other threads:[~2018-02-19  6:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22847-6586@http.sourceware.org/bugzilla/>
2018-02-15  6:01 ` mysecondaccountabc at gmail dot com
2018-02-15  6:09 ` mysecondaccountabc at gmail dot com
2018-02-15 15:45 ` dsmith at redhat dot com
2018-02-15 16:08 ` dsmith at redhat dot com
2018-02-16  4:06 ` mysecondaccountabc at gmail dot com
2018-02-19  6:55 ` mysecondaccountabc at gmail dot com [this message]
2018-02-19  7:02 ` mysecondaccountabc at gmail dot com
2018-02-19 14:31 ` dsmith at redhat dot com
2018-02-19 22:42 ` mysecondaccountabc at gmail dot com
2018-02-19 22:53 ` dsmith at redhat dot com
2018-02-20  1:05 ` mysecondaccountabc at gmail dot com
2018-02-20 16:03 ` dsmith at redhat dot com
2018-02-22  0:04 ` gmoreira at gmail dot com
2018-02-22 16:58 ` dsmith at redhat dot com
2018-04-18  6:50 ` gmoreira at gmail dot com
2018-04-18  6:52 ` gmoreira at gmail dot com
2018-04-18  7:05 ` gmoreira at gmail dot com
2018-04-18  7:26 ` gmoreira at gmail dot com
2018-04-30 17:16 ` dsmith at redhat dot com
2018-05-01  2:46 ` gmoreira at gmail dot com
2018-05-01 15:11 ` dsmith at redhat dot com
2023-10-06 15:55 ` wcohen at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-22847-6586-sRz8UAXDW5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).