Mail Archives: djgpp/2000/06/09/10:46:45
> From: Krogg <krogg DOT no DOT to DOT spam AT gtcom DOT net>
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 09 Jun 2000 05:27:54 -0400
> >
> > I'm guessing that you are using an old version of DJGPP, like v2.01.
> > That version had a bug in the library function that gets linked into
> > your application under -pg, and that bug could easily produce the
> > effects you are describing.
>
> That is one nasty bug...how does it blow out the
> timers?
The bug I was talking about didn't do anything to the timers, it just
caused the profiling code to try to write to the monochrome display,
which will surely slow down any program.
In DJGPP v2.02, there was another problem wth profiling, but it didn't
slow down programs, AFAIK.
> How would i know?....gcc says 2.95
One way is to look at the header file include/sys/version.h.
> > What version of Binutils do you use, btw? What does "gprof --version"
> > print?
>
> gprof says 2.8.1
That is also very old. But Gprof itself couldn't be the reason for
slow-down, because it is only run (by you) after the profiled program
exits.
> Is there some tool that i can use to keep up with
> what version i have of everything,and help me
> know what to download.....
The DJGPP mini-FAQ, posted weekly to comp.os.msdos.djgpp, shows the
latest versions of everything.
One way of finding out what versions do you have installed, is to look
at the *.ver files in your manifest directory.
- Raw text -