>This is a multi-part message in MIME format.
>Content-Type: text/plain; charset=us-ascii
> Does anyone know of a way to use the GNU profiler using REAL time
>and not just process virtual time? The reason is, that I want to see
>the time some functions are blocking (waiting for file locking to
>go through), and the current profiler output only lists time in
>the actual process.
That's what profiling is for; for seeing CPU usage. To do real time profiling,
use a hardware clock, like what is read by the ``rdtsc'' instruction on
Pentiums and some 486es. With the time-stamp counter, you can get a fine
grained measurement of how much time elapsed between two points in the
execution of the program.
The gettimeofday() system call will use the instruction if it's available;
however it takes time to make the system call; for greater accuracy you want
the instruction to be embedded in some inline code.
I'd make an abstract time-stamp counter class that can be implemented in
various ways depending on what is available, and which can be turned off
when not instrumenting.
>Content-Type: text/x-vcard; charset=us-ascii;
>Content-Description: Card for Seth Goldberg
>org:Sun Microsystems, Inc.;Strategic Partnerships
>title:Senior Systems Engineer
>adr;quoted-printable:;;20450 Stevens Creek Boulevard=0D=0AMS CUP03-403;Cupertino;California;95014;USA
Would you mind turning that off when posting to Usenet discussion groups?
Proper etiquette calls for signature lines that are no longer than four
lines, and for the avoidance of MIME attachments.