This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
problem tracing open syscalls
- From: Andreas Kostyrka <andreas at kostyrka dot org>
- To: systemtap at sources dot redhat dot com
- Date: Sun, 25 Feb 2007 16:58:20 +0100
- Subject: problem tracing open syscalls
Hi!
I'm trying to figure out what files are opened on my system, but I'm
not getting any sensible data:
#!/usr/bin/env stap
global syscalls
probe syscall.open {
printf("open %d %s\n", pid(), filename);
}
Produces only output like that:
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 9487 <unknown>
open 4516 <unknown>
open 4516 <unknown>
open 4485 <unknown>
open 4485 <unknown>
open 4485 <unknown>
open 4485 <unknown>
open 4485 <unknown>
open 4485 <unknown>
open 4485 <unknown>
That leaves the question how to access the filename being opened :(
Linux 2.6.20 on Debian, systemtap 0.0.20070113-1
TIA,
Andreas