Date:	Tue, 15 Mar 1994 10:14:48 -0700
From:	tesla AT lamar DOT ColoState DOT EDU (Jon Nash)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Compiler Aborst Why? (Update #2)

Well, the saga continues :)  I've tried all suggestions given...  -v, -S, even
adding topline to the GO32 environment variable.  When I did this several
numbers appeared at the top of the screen, something on the far left that
flickered between an R and a P (I think), an orange address in the middle,
a red memory counter that wasn't _always_ there but never went above 150 Kb
(which is well below the 6 Megs of RAM go32 says is available) and some other
numbers in the top left (another memory indicator that seemed to stay basically
constant at about 140 Kb, and some other symbol like a '>' or something).

I still got an Abort! but when topline was enabled the computer acted funny
after the compile aborted...  had to reboot...

DJ has offered to look at my code (325 lines of it) :) so I await his
esteemed words of wisdom!

Thanks to all who have helped!

Jon Nash
Tesla AT Lamar DOT ColoState DOT EDU
Colorado State University
Physics Department

- Raw text -