From: GAMMELJL AT SLU DOT EDU
Date: Wed, 22 Sep 1999 10:13:43 -0500 (CDT)
Subject: Problem with new malloc.c attn: Eli Zaretskii
To: djgpp AT delorie DOT com
Message-id: <01JG9MV9JK9U8WZVG8@SLU.EDU>
Organization: SAINT LOUIS UNIVERSITY  St. Louis, MO
X-VMS-To: IN%"djgpp AT delorie DOT com"
MIME-version: 1.0
Content-type: text/plain
Reply-To: djgpp AT delorie DOT com

     What happens when I try to run the compiled program
                          c:\codename
is this:  many screens of error information scroll by with
no stopping until I press "pause". To resume I press the
space bar.  Then a few more screens scroll by and finally
the scrolling stops.
     I reason that I had better look at the output one screen
at a time so I use
              c:\codename | more.
Lo and behold, the program runs, and every run thereafter with
or without the | more is successful.
     If I recompile the source code and run without the | more
the endless scrolling re-occurs.  Again, running with | more is
successful, and runs thereafter with or without the | more are
successful.
     The same remarks apply if instead of | more I redirect the
output to a file using
              c:\codename >error.txt.
     Now, I really did not understand what it is that you want
me to post.  I assume that it is the error messages resulting
from running the code, which I cannot capture in view of the
above.  If my assumption is incorrect, please give me more
detailed instructions about how to run and capture the infor-
mation you want.
     I can hand copy the last bit of the error messages going
to the screen: 
        Exiting due to signal SIGSEGV
        General Protection Fault at
               eip=00001f47
        eax=6574649 .................................
        .................exp=0005c380 program=c:\codename.exe
        cs=set 0097 base 10000000 limit=0006ffff
        .
        .
        ss
        Call frame traceback EIPs:
        0x00001f47
        .
        .
        0x6f697461
I could hand copy what I have omitted if it is of any use to you.

     Another fact (whose relationship to the above I cannot
imagine) is that if I delete the destructors (see the lines
marked "destructor for realmp" in the example which I posted)
from my class definitions I do not have any problem compiling
and running with the new malloc.c. even with large, realistic
programs and that, so long as I have no better solution to
the problem, is what I do.