Message-Id: <5.0.1.4.0.20001116230739.00a55af0@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Thu, 16 Nov 2000 23:21:57 -0500
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Help: Isn't libdbg the debugging version of libc?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Reply-To: djgpp-workers AT delorie DOT com

OK, I'm trying to debug Mark E.'s enhanced fcntl, but gdb won't step 
into any libc function.  I tried adding libdbg here in the file 
"tests\makefile.inc":

C = ${LIB}/crt0.o
L = ${LIB}/libdbg.a

but that leads to linker errors (missing entry points of various 
kinds).  Looking at the size of libdbg.a, I now understand that it 
could not be a debugging version of libc.a, because it has very little 
inside of it.

Can you point me at any info or docs on the right way to make and use a 
debugging version of libc for gdb testing of fcntl?

BTW, the current "tests\makefile.inc" expects libgcc.a to be in the 
"${LIB}" directory, but it is now in "${LIB}/gcc-lib/djgpp/2.952".  I 
had to update "tests\makefile.inc" to change that assumption.

Secondary question:  Why are we including libgcc.a in the LINK step in 
"tests\makefile.inc"?  Aren't we trying to test libc.a?  What knowledge 
am I missing here?

TIA for any info or assistance you can provide.

---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)