Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpcc01!hpcuhb!hpda!hpcupt1!hprnd!fraley
From: fraley@hprnd.HP.COM (Andy Fraley)
Newsgroups: comp.windows.ms
Subject: Re: Debuggers and DLLs
Message-ID: <6120004@hprnd.HP.COM>
Date: 2 Jul 90 22:08:46 GMT
References: <292600020@trsvax>
Organization: HP Roseville Networks Division
Lines: 29

/ hprnd:comp.windows.ms / reyn@trsvax.UUCP /  9:00 am  Jun 29, 1990 /

For those who have already developed applications for Windows 3.0 ...
   prefereably for those who have also developed a DLL ...

> Which debugger do you find the most useful for development ( CodeView,
> Turbo Debugger, Periscope, Symdeb, etc. )

I find CodeView adequate for most things.

> I have no experience with Windows, but in the DeskMate environment most
> debuggers just didn't cut it when developing DLLs ( DeskMate calls them
> resources ).  When debugging the code in the DLL it is necessary to load (
> or switch to ) a seperate symbol table from the one which you need to debug
> the app itself.  CodeView can't ( I should say couldn't ) do this,
> Periscope and Symdeb can.

I use CodeView (CVW) to debug my DLLs in protected mode, SYMDEB to
debug in real mode.  For CodeView, just compile the DLL modules with
-Zi and link with /CO.  Run CVW in Windows 3.0 and specify the DLL's
parent application as the application to run.  If there is no debug
info compiled into the parent, you'll get a warning message which you
can ignore.  CodeView then asks you to "Name an other DLL or
executable with debug info."  Just type in the name of the DLL with
the debug info.  For more information, see the Windows 3.0 SDK
manuals.

-Andy Fraley
 HP Roseville Networks Division