Date: Mon, 4 Jun 2001 20:33:38 -0400
Message-Id: <200106050033.UAA29487@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
CC: awhite AT mail DOT rosecom DOT ca
In-reply-to: <3B1C2662.A2575F0D@mail.rosecom.ca> (message from April on Mon,
	04 Jun 2001 20:22:58 -0400)
Subject: Re: gprof question
References:  <3B1C2662 DOT A2575F0D AT mail DOT rosecom DOT ca>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> I realize that this is a very ambiguous question, but what generally
> causes these interrupts to fire?  The program runs for about 50 seconds,
> and more than 30 seconds apparently are taken up by calls to this
> interrupt.  If I can acertain what causes it to fire, I might be able to
> alter my code and reduce this significant overhead - I hope :-)

Anything that does an OS call - read, time, sbrk (used by malloc),
sometimes getkey().