Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!samsung!emory!hubcap!ncrcae!ncr-sd!se-sd!lowery
From: lowery@se-sd.SanDiego.NCR.COM (Tim Lowery)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: CodeView in the Microsoft C 6.0 PWB
Keywords: ibm pc Microsoft C 6.0 PWB codeview
Message-ID: <3172@se-sd.SanDiego.NCR.COM>
Date: 5 Jun 90 16:20:51 GMT
Reply-To: lowery@se-sd.SanDiego.NCR.COM (Tim Lowery)
Followup-To: comp.sys.ibm.pc.programmer
Distribution: usa
Organization: NCR Corporation, Systems Engineering - San Diego
Lines: 15

I recently received my update to Microsoft C 6.0.  This release contains
a "complete" development environment (i.e. editor, make facilities, debugger,
source browser/cross referencing tool) with pull-down menus and mouse support.
Overall it looks pretty good.  However, I'm having trouble generating an
.EXE file with CodeView symbol table information from within the menu
system.  If I enter the compile and link commands directly from the DOS
command line (with the appropriate options for CodeView) I get CodeView
source level debugging information compiled into my file, no problem.
However, if I set the options in the menu system (Microsoft calls it the
Programmer's Workbench or PWB) to compile for CodeView and do a make, when
I then go into CodeView I am informed that there is no symbol table information
available for source level debugging.  I am then invited to do my debugging in
assembly language.  Is anyone out there in net land aware of a bug in
the 6.0 programmer's workbench?  Have I overlooked something (I set all
the appropriate Build, Compile, and Link options as per the manual)?