Mail Archives: djgpp/2002/02/10/02:17:32
> DJ Delorie wrote:
> >
> > Make sure malloc.c is including xmalloc.h from the libc source, not
> > some other xmalloc, and that it has access to <libc/malloc.h>.
>
> Now what is this? There is no xmalloc.h reference in the malloc
> source? There is no xmalloc.h on my system.
Ignore this advice unless you download the V2.04 work in progress from
CVS. xmalloc.h is part of the restructured malloc (new) but is not used
or needed by the V2.03 source version.
> Would you please go back to my previous post and answer the
> specific questions, which I requote below:
>
> "however the same command seems to function if I eliminate the -W
> -Wall -ansi -pedantic -gstabs+ default flags by using *gcc.
These are not default flags in GCC. (I don't know where these are
coming from? Are you using a command line or ?). You don't actually
need any of them (and some may be causing the compile problems).
Something like gcc -c -O2 -pg malloc.c should do it.
> ... Obviously the only portion that needs profiling
> is the malloc.c content, and that should be as detailed as
> possible. Should I be using gstabs+, gstabs, or g? The other
> modules are compiled with the defaults above. Does that matter?"
It doesn't matter. Since malloc.c is not C++ you don't gain much
from the extra debugging info. We really are looking for profile
information here.
Thanks.
- Raw text -