newbie question

[Daniel Jacobowitz]

On Tue, Mar 11, 2003 at 09:50:35PM +0100, Jonas Geiregat wrote:
> When I use strace /bin/echo foobar
> I get this output
> strace -c /bin/echo foobar   
> execve("/bin/echo", ["/bin/echo"], [/* 64 vars */]) = 0
> 
> % time     seconds  usecs/call     calls    errors syscall
> ------ ----------- ----------- --------- --------- ----------------
> 29.26    0.000189           7        29        13 open
> 27.24    0.000176         176         1           write
> 16.56    0.000107           8        14           mmap2
>  7.12    0.000046          15         3           read
>  5.42    0.000035           2        17           fstat64
>  4.64    0.000030           2        16           close
>  3.25    0.000021           4         5           old_mmap
>  2.94    0.000019           6         3           munmap
>  2.32    0.000015           2         7           brk
>  0.62    0.000004           4         1           uname
>  0.62    0.000004           4         1           mprotect
> ------ ----------- ----------- --------- --------- ----------------
> 100.00    0.000646                    97        13 total
> 
> Now I don't get much of what is outputted and there is not much info 
> about this output in the man pages
> I want to know how many sys call he made/used for executing this binairy
> I just can't believe he made 97 for this simple programma
> and what could errors syscall mean any info would help

Sure, depending on your system, maybe there were 97.  A modern
GNU/Linux system has 29.  97 isn't unreasonable.

Errors is the number of syscalls which returned an error value. 
Probably attempts to open a library that doesn't exist.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer