From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: gprof with all zero execution times in version 2.03
Date: Tue, 13 May 2003 09:26:12 CDT
Organization: Rice University, Houston, TX
Lines: 16
Message-ID: <3ec10084.sandmann@clio.rice.edu>
References: <b9qegc$b4g$1 AT antares DOT lu DOT erisoft DOT se> <5c9be5c2 DOT 0305130608 DOT 3d3661ef AT posting DOT google DOT com>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1052836058 226 128.42.105.3 (13 May 2003 14:27:38 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: Tue, 13 May 2003 14:27:38 +0000 (UTC)
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> I got this output sample after running the program for approximately
> 45 minutes, not 0.28 seconds...

Were you running on a Windows system?  If so, they quite often don't bother
to send timer interrupts (especially if the program is in the background).
Try running under DOS for more accurate profiling.

> > :   %   cumulative   self              self     total           
> > :  time   seconds   seconds    calls  Ts/call  Ts/call  name    
> > : 100.00      0.28     0.28                             __dpmi_int
> > :   0.00      0.28     0.00  7382040     0.00     0.00  crc_inc

Even without timing information, it's clear you have over 7 Million
calls to crc_inc - so you are spending all of your time in that 
routine.