Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!psivax!quad1!few
From: few@quad1.quad.com (Frank Whaley)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Need help Turbo Debugging code in a library
Keywords: Turbo TD386 tlib tlink
Message-ID: <14876@gouda.quad.com>
Date: 7 Sep 90 05:58:31 GMT
References: <1990Sep6.174743.13108@odin.corp.sgi.com>
Distribution: na
Organization: Quadratron Systems, Westlake Village, CA
Lines: 20

In article <1990Sep6.174743.13108@odin.corp.sgi.com>,
nelson@bolyard.wpd.sgi.com (Nelson Bolyard) writes:
>Recently, I used tlib to put a bunch of my .OBJ files into a .lib file
>and changed my makefile to have tcc pick up the .lib file.  When I tried
>to step through the .exe with TD386, I discovered to my dismay that all the
>debugging information for the code in the library was absent from the .exe
>file.  The TD386 CPU window showed me no line number information nor source 
>for any of the routines in the library.

Your error was in using TLINK.  For some unfathomable reason the 2.0 version
of TLINK strips symbolic debugging information.  Other library managers do
not do this.  I use Plib86 because they include a time-stamp that is
recognized by my make program, although LIB otherwise works just as well.
-- 
Frank Whaley
few@quad1.quad.com
uunet!ccicpg!quad1!few

Water separates the people of the world;
Wine unites them.