🚀 go-pugleaf

In article <1992Oct27.203656.7919@panix.com>, os2man@panix.com (Larry Salomon Jr.) writes:
> Now's the time when I wish I had my home-grown versions of malloc() here at
> the office...
> 
> I'm experiencing sporadic traps in my application that I cannot attribute
> to anything.  However, I do a *large* number of malloc()/free() combinations.
> I am 99% certain that I am not calling free() twice with the same pointer.
> Does anyone know if the MSC 6.0 runtime (notice that I do not have the 
> service upgrade) has/had any problems with memory allocation?

I have never used 6.0, but the docs from 6.00A say:


                               C60AFIX.DOC File

             Release Notes for the Microsoft(R) C Professional
                      Development System, Version 6.0A

                  (C) Copyright Microsoft Corporation, 1990
                                          
     This document contains release notes for version 6.0A of the
     Microsoft C Professional Development System.

     Microsoft C version 6.0A provides fixes for many of the possible
     compiler errors in the previous release of C 6.0.


================================< Contents >================================

  
     This file has two parts:
  
               Part     Note
               ----     ----
               1        Problems Fixed in This Release

               2        New Product Support Services Phone Number


================< Part 1: Problems Fixed in this Release >==================

 
     Internal Compiler Errors
     ------------------------
 
     A number of Internal Compiler Errors (ICEs) were addressed in
     the C 6.0A update. Many of these were apparent only when a
     specific combination of optimization and memory models was used.
     Internal Compiler Errors generate the following text:

          fatal error Cnnnn: Internal Compiler Error
          (compiler file) '@(#)regMD.C : 1.100
          Contact Microsoft Product Support Services
 
 
     Code Generation Errors
     ----------------------
 
     In some very specific instances, C 6.0 did not generate the
     correct executable code for the corresponding C language code.

     In C 6.0, some code-generation errors were associated with high
     levels of optimization. Symptoms of a code generation problem
     vary from incorrect execution of a function to a system hang, and
     are usually unpredictable.

     If you experienced what might have been code generation problems
     with C 6.0, please retry compiling the code in question under C
     6.0A.
 
 
     Optimization
     ------------
 
     If you had compile-time errors under C 6.0 which disappeared when
     optimization was turned off, you should try to recompile your
     code using C 6.0A.

     A variety of optimization-related problems were addressed with this
     release:

        - Internal compiler errors
        - Incorrect code generation
        - Loops that were not functioning correctly


     OS/2-Specific Fixes
     -------------------
 
     C 6.0A includes a variety of OS/2-related fixes. Several errors
     that caused segmentation violations and general protection (GP)
     faults were eliminated.

     Problems with the multithreaded versions of ecvt() and fcvt()
     were also fixed.


     Incorrect Errors & Warnings
     ---------------------------
 
     Occasionally, C 6.0 reported errors or warnings that were not
     appropriate or correct. These have been fixed.

 
     Problems with Structures
     ------------------------
 
     C 6.0 contained some errors in the way structures were
     handled. Possible sources of errors included the following:

        - Structures with an odd number of bytes (possible when
          using the /Zp compiler switch or the pack pragma)
        - Unnamed structures
        - Nested structs

     C 6.0A has fixed the known problems with C-language structs.
 

===============< New Product Support Services Phone Number >================


     The number for Microsoft Product Support Services (Languages) is
     206-637-7096.

-- 
--Darrel Hankerson hank@ducvax.auburn.edu