Xref: utzoo comp.lang.c:14704 comp.sys.ibm.pc:22174
Path: utzoo!attcan!uunet!mcvax!unido!tub!astbe!mey
From: mey@astbe.UUCP (Thomas Meyer)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Difficulties with Turbo-C 2.0 TLIB
Keywords: TLIB 2.0 considered harmful (:-))
Message-ID: <458@astbe.UUCP>
Date: 13 Dec 88 10:13:26 GMT
Reply-To: mey@astbe.UUCP (Thomas Meyer)
Organization: GEI Software Technik Berlin, Germany
Lines: 27

We are using Turbo C 2.0, its TLIB utility and the stand-alone debugger TD.
Recently I discovered the following effect. I created a library  containing
modules, which were compiled with debug options. 

The manual states, that debugging of modules in libraries *is* possible, 
provided that

	- the modules were compiled with debug option set,
	- the library was *not* created with the "Create Extended Dictonary"
	  option,
	- the source code of the modules is available and
	- the source code directory option in Turbo Debug is set appropriately.

Though those conditions were fulfilled, the debugger refused to show 
the source code of libary functions. Worse, the programme crashed, when the
the first function in the library was called. (The library is quite big,
about 200K)

Finally I resolved the problem by using the TLIB utility which came along with
Turbo C 1.5, which does the job fine and allowes me to debug modules stored
in libraries.

Did anyone had similar experiences and can give an explanation ?
Are there more known bugs ?

Inspite of this time-consuming experience Turbo C 2.0, especially its
stand-alone debugger, surpassed our expectations.