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


On what processor architecture do you run systemtap. And what compiler
you used to compile kernel? Is '4485' in your example PID of existing
process?

25 ÐÑÑÐÐÐ 2007 Ð 21:18 +0100 Andreas Kostyrka ÐÐÐÐÑÐÐ(-ÐÐ):
> 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.

-- 
Eugeniy Meshcheryakov

Attachment: signature.asc
Description: Digital signature


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