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]

Re: problem tracing open syscalls


I've upgraded to 
ii  systemtap      0.0.20070217-1              instrumentation system for Linux 2.6

and I'm getting the same behaviour :(

One additional thing are the skipped probes, however one wants to
interpret it:
open 4485 <unknown>
open 4485 <unknown>
open 4485 <unknown>
WARNING: Number of errors: 0, skipped probes: 2073
Pass 5: run completed in 60usr/110sys/34870real ms.

Andreas


* Eugeniy Meshcheryakov <eugen@debian.org> [070225 20:25]:
> Hello,
> 
> 25 ÐÑÑÐÐÐ 2007 Ð 16:58 +0100 Andreas Kostyrka ÐÐÐÐÑÐÐ(-ÐÐ):
> > 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);
> > }
> I tried to run this script with systemtap 20070217 and kernel
> 2.6.21-rc1, and it works. Could you try this systemtap version (it is in
> unstable now)? Also, on what architecture do you run this script?
> 
> > 
> > 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
> > 
> 
> -- 
> Eugeniy Meshcheryakov



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