So I rewrote the perl program and the C program to write to the same text file
I get something like this in my output.txt:
237 time system call 8 238 time system call 8 239 time system call 5 240 time system call 5 241 time system call 72 242 time system call 72 243 time system call 1 Started #The BEGIN block 244 time system call 1 245 time system call 3 246 time system call 3 247 time system call 2 248 time system call 2 249 time system call 8 250 time system call 8 251 time system call 16 252 time system call 16 253 time system call 8 254 time system call 8 255 time system call 5 256 time system call 5 257 time system call 72 258 time system call 72 259 time system call 1 hello world 260 time system call 1 261 time system call 3 262 time system call 3 .... .... At 400 about I get the END block print and then 3 more system calls before termination
Unfortunately I don't know now when I should start monitoring the target problem. I want to write something of a generic tracer for any perl script. I thought I would see a pattern in the perl interpreter's system calls but I don't. Any ideas?
In reply to Re^2: tracing system calls a perl script is making
by gideondsouza
in thread tracing system calls a perl script is making
by gideondsouza
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |