Re^2: tracing system calls a perl script is making

[gideondsouza]

That was a really eloquent solution!

Unfortunately I think my reading stdout with pipes is flawed! :( I get all the "starting" "hello" and "ending code" just all together after all the 367 system calls and printed.

And this is because I'm reading the pipes after the program exits

Any ideas for other approaches?

Thanks for your answer though! After 1 month of side lining this I realize today my approach is slightly flawed!

[shmem]

Unfortunately I think my reading stdout with pipes is flawed!

Not necessarily so. More probably you are "suffering from buffering":

• printing to the terminal is line buffered
• printing elsewhere is block buffered

Try inserting

$| = 1;

at the top of your program. See perlvar.

[BrowserUk]

I get all the "starting" "hello" and "ending code" just all together after all the 367 system calls and printed.

Replace print with print STDERR ...; (or use warn).