This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

AW: strace.open does probe does not fire

From: Wolfram Gettert <Wolfram dot Gettert at mixed-mode dot de>
To: "systemtap at sourceware dot org" <systemtap at sourceware dot org>
Date: Wed, 26 Jun 2019 08:33:37 +0000
Subject: AW: strace.open does probe does not fire
References: <28efd687dcd14c478a0e555ff70cbd43@lippe.pixel-group.local> <3a906c05-da55-e325-b7e9-3bfaa36cacdb@redhat.com> <CANA-60oPKertzvHs8pGqS68+3Z1N3KVz-hpg6q7sOwFWG0k-og@mail.gmail.com>

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

References:
- strace.open does probe does not fire
  - From: Wolfram Gettert
- Re: strace.open does probe does not fire
  - From: Josh Stone
- Re: strace.open does probe does not fire
  - From: Arkady

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]