Re: problem tracing open syscalls

[Eugeniy Meshcheryakov <eugen at debian dot org>]

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

Attachment: signature.asc
Description: Digital signature