Path: utzoo!attcan!uunet!snorkelwacker!apple!vsi1!octopus!stever From: stever@Octopus.COM (Steve Resnick ) Newsgroups: comp.os.msdos.programmer Subject: Re: Need help Turbo Debugging code in a library Keywords: Turbo TD386 tlib tlink Message-ID: <1990Sep7.142347.8232@Octopus.COM> Date: 7 Sep 90 14:23:47 GMT References: <1990Sep6.174743.13108@odin.corp.sgi.com> <26035@cs.yale.edu> Reply-To: stever@octopus.UUCP (Steve Resnick ) Organization: Octopus Enterprises, Cupertino CA Lines: 27 In article <26035@cs.yale.edu> spolsky-joel@cs.yale.edu (Joel Spolsky) writes: >In article <1990Sep6.174743.13108@odin.corp.sgi.com> nelson@bolyard.wpd.sgi.com (Nelson Bolyard) writes: >>If you can help me get TD386 to debug TC code linked from a library, I'd >>greatly appreciate it! > >You can't include symbollic debugging information in libraries, only >in .OBJ files. The /E flag does not do what you think (it just makes >it easier to find things in the library). The idea is that you debug >your object modules completely before putting them into libraries. > Sure you can - or at least I could. I compiled a bunch of .OBJ files with the -v flag set (this also implies -y), used -G- -Z- -O- to disable any optimizations. I linked my program using tcc as the "front-end" to the linker. When I ran the program I got the symbolic and line number info for one of the library routines. Getting creative, I moved the source file for that routine into my current directory and , voila! I was able to trace thru my library routine. Hope this helps.... Steve -- ---------------------------------------------------------------------------- steve.resnick@f105.n143.z1@FIDONET.ORG #include Flames, grammar errors, spelling errrors >/dev/nul ----------------------------------------------------------------------------