Date: Wed, 17 May 1995 08:21:18 +0500 From: hvb AT netrix DOT com To: Rick Bronson , Eric Heft Cc: hvb AT netrix DOT com, djgpp AT sun DOT soe DOT clarkson DOT edu Subject: Re: General question References: <9505161815 DOT AA02649 AT azalea> <9505170338 DOT AA02667 AT rio> Rick Bronson writes: > > Hung, > Thanks for the response. You just use plain gcc that is set to > cross compile for X86 and go32, right? What do you use for debugging of the > executable on MSDOS? > > Thanks again. > > Rick I did not build the gcc tool so I am not certain, but I believe it is just from the standard distribution. About debugger there are at least two full screen debuggers: - edebug32 which came with DJGPP go32 package - Ladybug which is a modified version of edebug32. Ladybug has different user's interface as Ladybug allows us to debug from an ANSI terminall attached to a comm port. It also has a built in performance analyzer for you to produce a histogram of percentage of time where the CPU spends its processing (in Protected mode). Long Doan, who wors for us (Netrix), modified edebug32 and formed Ladybug. We, therefore, use Ladybug all the time. We have the comm port connected to our Sun or HP Apollo work station and debug from there. This way we can always view the source code on the same screen. I believe, both debuggers can display C source code if you have the C source file loaded on the PC. We do not use them, as the diassebled display always give us the module/line number info which is over ninety percent of what we need during debugging. Downloading source code can be a real pain if you want all the files to be up to date. Hope this helps. ============================================================== Hung Bui Internet: h DOT bui AT ieee DOT org Netrix Corporation Phone: +1 703 793 1016 13595 Dulles Technology Drive Fax: +1 703 713 3805 Herndon Va 22071 ==============================================================