* strace.open does probe does not fire
@ 2019-06-24 11:43 Wolfram Gettert
2019-06-24 21:13 ` Josh Stone
0 siblings, 1 reply; 4+ messages in thread
From: Wolfram Gettert @ 2019-06-24 11:43 UTC (permalink / raw)
To: systemtap
Hi,
I am executing the following script:
----
probe begin
{
printf("Start probing syscall.open\n")
}
probe syscall.open
{
printf ("%s(%d) open(%s)\n", execname(), pid(), argstr)
}
probe timer.s(10)
{
exit ()
}
probe end
{
printf("Stop probing syscall.open\n")
}
----
I get the "Start probing syscall.open" and the "Stop probing syscall.open" message. I am executing "cat /dev/null" calls in a shell to be sure there is an open call. But the syscall.open probe does not fire.
I am using Ubuntu 18.04.2 LTS with Systemtap translator/driver (version 4.0/0.170, non-git sources).
I know that this script already worked for me on older versions. Is there anything what has changed?
Does anyone has an idea why it should not work?
Wolfram
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: strace.open does probe does not fire
2019-06-24 11:43 strace.open does probe does not fire Wolfram Gettert
@ 2019-06-24 21:13 ` Josh Stone
2019-06-25 16:08 ` Arkady
0 siblings, 1 reply; 4+ messages in thread
From: Josh Stone @ 2019-06-24 21:13 UTC (permalink / raw)
To: Wolfram Gettert, systemtap
On 6/24/19 4:43 AM, Wolfram Gettert wrote:
> I get the "Start probing syscall.open" and the "Stop probing syscall.open" message. I am executing "cat /dev/null" calls in a shell to be sure there is an open call. But the syscall.open probe does not fire.
On my Fedora 30, "cat /dev/null" only calls "openat", not "open".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: strace.open does probe does not fire
2019-06-24 21:13 ` Josh Stone
@ 2019-06-25 16:08 ` Arkady
2019-06-26 8:33 ` AW: " Wolfram Gettert
0 siblings, 1 reply; 4+ messages in thread
From: Arkady @ 2019-06-25 16:08 UTC (permalink / raw)
To: Josh Stone; +Cc: Wolfram Gettert, systemtap
On Tue, Jun 25, 2019 at 12:13 AM Josh Stone <jistone@redhat.com> wrote:
>
> On 6/24/19 4:43 AM, Wolfram Gettert wrote:
> > I get the "Start probing syscall.open" and the "Stop probing syscall.open" message. I am executing "cat /dev/null" calls in a shell to be sure there is an open call. But the syscall.open probe does not fire.
>
> On my Fedora 30, "cat /dev/null" only calls "openat", not "open".
Josh, glibc will use openat syscall
^ permalink raw reply [flat|nested] 4+ messages in thread
* AW: strace.open does probe does not fire
2019-06-25 16:08 ` Arkady
@ 2019-06-26 8:33 ` Wolfram Gettert
0 siblings, 0 replies; 4+ messages in thread
From: Wolfram Gettert @ 2019-06-26 8:33 UTC (permalink / raw)
To: systemtap
Hallo Josh,
thanks a lot.
I was not aware of this syscall. That fixes my problem.
Wolfram
-----Ursprüngliche Nachricht-----
Von: Arkady [mailto:arkady.miasnikov@gmail.com]
Gesendet: Dienstag, 25. Juni 2019 18:08
An: Josh Stone
Cc: Wolfram Gettert; systemtap@sourceware.org
Betreff: Re: strace.open does probe does not fire
On Tue, Jun 25, 2019 at 12:13 AM Josh Stone <jistone@redhat.com> wrote:
>
> On 6/24/19 4:43 AM, Wolfram Gettert wrote:
> > I get the "Start probing syscall.open" and the "Stop probing syscall.open" message. I am executing "cat /dev/null" calls in a shell to be sure there is an open call. But the syscall.open probe does not fire.
>
> On my Fedora 30, "cat /dev/null" only calls "openat", not "open".
Josh, glibc will use openat syscall
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-06-26 8:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-24 11:43 strace.open does probe does not fire Wolfram Gettert
2019-06-24 21:13 ` Josh Stone
2019-06-25 16:08 ` Arkady
2019-06-26 8:33 ` AW: " Wolfram Gettert
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).