KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q66230: Running Out of Memory in CodeView with /X

Article: Q66230
Product(s): See article
Version(s): 3.00 3.10 3.11
Operating System(s): MS-DOS
Keyword(s): ENDUSER | | mspl13_basic
Last Modified: 24-OCT-1990

Under some circumstances, CodeView may still run out of memory while
debugging large applications with the /X switch invoked to take
advantage of extended memory with HIMEM.SYS. The debug information
gets expanded when CodeView loads the program, so the following
suggestions may help the problem:

1. Don't use the quick compile (/qc) option. The symbolic information
   created by the quick compiler may expand much more when loaded by
   CodeView than the symbolic information created by the standard
   compiler. In addition, the quick compiler may create some duplicate
   debug references in the executable file. These duplicate references
   can take up significant memory when CodeView loads the program.

2. Use the CVPACK utility, which is documented in the online
   documentation and on Page 21 of the "Microsoft C Reference" manual.
   CVPACK will compress the debug information in the file by removing
   duplicate references. Use the /P option to achieve maximum
   compression.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.