Mail Archives: djgpp/2002/02/09/23:00:25
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.
>
> > Should I be using gstabs+, gstabs, or g?
>
> I think what you want is -pg, not -gp.
As I read the info, to get detailed line by line data you had to
compile with debug info. So please answer the question again. See
below
>
> If you compile any module with -pg, you need to link with -pg also.
>
> > I assume that if malloc is linked before the library search the
> > library version will be omitted?
>
> Yes.
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. What
do I really need? 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?"
--
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT XXXXworldnet DOT att DOT net)
Available for consulting/temporary embedded and systems.
(Remove "XXXX" from reply address. yahoo works unmodified)
mailto:uce AT ftc DOT gov (for spambots to harvest)
- Raw text -