Newsgroups: comp.sys.cbm
Path: utzoo!utgpu!jarvis.csri.toronto.edu!godzilla.eecg!leblanc
From: leblanc@eecg.toronto.edu (Marcel LeBlanc)
Subject: Re: Where's the load file name?
Message-ID: <1989Jun13.132621.16783@jarvis.csri.toronto.edu>
Summary: FC III bashing
Organization: EECG, University of Toronto
References: <7000016@silver> <1235@cbnewsc.ATT.COM>

In article <1235@cbnewsc.ATT.COM> carus@cbnewsc.ATT.COM (bryce.w.carus) writes:
>In article <7000016@silver>, rschofie@silver.bacs.indiana.edu writes:
 ...
>If you can control the point in time where you wish to read the locations noted
>then you'll have no problems. If not, you may be able to use FC III's freeze
>capability and monitor to read them.

Not if it's like the FC II that I've played with! :-) FC's corrupt the lower
2K of memory ($0000-$07FF) when you enter the monitor.  I think FC III is
the same.  It's very difficult for the FC to get around this because it
must use this area of memory, and it has no place to save a temporary copy.
This is why you can't resume execution of the 'frozen' program after
entering FC's monitor.

Marcel A. LeBlanc	  | University of Toronto -- Toronto, Canada
leblanc@eecg.toronto.edu  | also: LMS Technologies Ltd, Fredericton, NB, Canada
-------------------------------------------------------------------------------
UUCP:	uunet!utai!eecg!leblanc    BITNET: leblanc@eecg.utoronto (may work)