From: byrne AT katie DOT vnet DOT net (Paul Byrne)
Newsgroups: comp.os.msdos.djgpp
Subject: profiling problems...
Date: 13 Feb 1998 04:12:10 -0500
Organization: Vnet Internet Access, Inc. - Charlotte, NC. (704) 374-0779
Lines: 27
Message-ID: <6c12pa$gf7$1@katie.vnet.net>
NNTP-Posting-Host: 166.82.1.7
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

I seem to be having problems getting profiling to work correctly.
At first, everything compiled just fine, but the program crashed
my machine when run.  After looking through the faq (gasp!) and a
little searching on the net I'm led to believe that a workaround
is to make sure that a certain range of memory is free.  And
indeed adding an option to emm386 in config.sys seems to help quite
a bit.  Now things seem to work well for quick programs, but if
the program takes a while to run it somehow ends up in an infinite
loop (maybe?).  Hitting ^C to break out after a while does
create a gmon.out file (I thought the program had to exit normally?).
The report from gprof only accounts for about 10 seconds of computation.
I ran it again and let it go for an hour or so, stopped the program
and gprof accounts for 30 seconds.  (Without profiling the program
exits normally in about 5 minutes.)  It does seem to be consuming CPU
time, it's just not doing anything.

Any ideas what's going on here?  Is this related to the emm386 thing,
or something else?

I notice that there's a patch to fix a problem in the profiling code.
Anyone know if there is a patched binary available anywhere?
I only downloaded djgpp a couple of days ago, and I'm having enough
problems getting my own code to work, never mind trying to recompile
part of the compiler...

Any help greatly appreciated!
-paul