Date: Mon, 10 Jan 2000 13:19:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: David Cleaver <davidis AT ou DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: another gprof problem
In-Reply-To: <3879196E.8B3DF7E3@ou.edu>
Message-ID: <Pine.SUN.3.91.1000110131938.6993C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 9 Jan 2000, David Cleaver wrote:

> C:\MyPrograms\CFiles>gprof -b prime
> Flat profile:
> 
> Each sample counts as 0.055556 seconds.
>   %   cumulative   self              self     total
>  time   seconds   seconds    calls  Ts/call  Ts/call  name
> 100.00      0.06     0.06                             __umoddi3
>   0.00      0.06     0.00        2     0.00     0.00  fxn1
>   0.00      0.06     0.00        1     0.00     0.00  isPrime
>   0.00      0.06     0.00        1     0.00     0.00  main
>   0.00      0.06     0.00        1     0.00     0.00  fxn4

This is a known bug in DJGPP v2.02 library (and the primary motivation
for v2.03 ;-).  The solution is to upgrade to DJGPP v2.03, released
two days ago, and rebuild your program.  Then run it again, invoke
gprof, and you should see a profile that makes sense.