delorie.com/archives/browse.cgi | search |
From: | "Deathifier" <storey AT tig DOT com DOT au> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Include a library code in the debug information of the program |
Date: | Fri, 16 Oct 1998 22:31:52 +1000 |
Organization: | The Internet Group Ltd |
Lines: | 36 |
Message-ID: | <707epu$969$1@toto.tig.com.au> |
References: | <36270ec9 DOT 576018 AT news DOT idecnet DOT com> |
NNTP-Posting-Host: | p25-max23.syd.ihug.com.au |
X-Newsreader: | Microsoft Outlook Express 4.72.3155.0 |
X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.3155.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Hello, I think you need to compile the actual library file with debugging info. Sorry, but I don't know much more than that. Cya, David Storey - Deathifier José Ignacio Merino Martín wrote in message <36270ec9 DOT 576018 AT news DOT idecnet DOT com>... > Hi! > > If you compile a program with the option -g, the compiler >includes all the information for debug. But only includes de code of >the main program. > > This is my problem because I'm developing a library and I'd >like trace it but I can't do it because the compiler only includes the >code of the main program. > > Anybody knows what can I do for include the code of one >library in the debug information of the program? > > Or maybe if there is any Developer Environment that when you >are debuggin a funtion in a library, show it and trace the function? > > Thanks. > > Jose Ignacio Merino Martin > jimerino AT NOSPAMidecnet DOT com > > (Quit NOSPAM from my e-mail) > >
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |