Mail Archives: djgpp/2002/02/11/01:24:24
On Mon, 11 Feb 2002, CBFalconer wrote:
> > [1] c:\c\hashlib>*gcc -c -pg -a -O2 -W -Wall -gstabs+ malloc.c
> >
> > [1] c:\c\hashlib>gcc -pg -a -o hshtestp hashtest.o cokusMT.o hashlib.o malloc.o
> >
> > [1] c:\c\hashlib>timerun hshtestp 4 10000
> > Timer 3 on: 22:39:40
> >
> > Your program caused a divide overflow error.
> > If the problem persists, contact your program vendor.
What version of GCC is this?
> dwpmi also shows up, but this is probably an effect, not a cause.
Sorry, I don't understand this comment. What DPMI functions appeared
hight in the profile, and why do you think it's an effect of something?
Perhaps simply post the flat profile part (the first part of Gprof's
output), in case there are some hints there that you overlooked.
> Now what?
Try invoking Gprof with the --line option, it might tell more about the
parts of `free' that take most of the running time.
> > Timer 3 off: 22:42:17 Elapsed: 0:00:02.80
Is this 2.8 seconds elapsed? If so, it might be too short for a
meaningful profile, especially if you succeed in getting line by line
information. Can you modify your program so that it runs longer, by
either enlarging the amount of allocated objects, or even by simply
running the same code in `main' in a loop?
- Raw text -