Path: utzoo!attcan!uunet!husc6!rutgers!mcnc!rti!rcb
From: rcb@rti.UUCP (Randy Buckland)
Newsgroups: comp.sys.mac.programmer
Subject: LSP 2.0 bug or corruption?
Message-ID: <2598@rti.UUCP>
Date: 28 Nov 88 04:49:21 GMT
Reply-To: rcb@rti.UUCP (Randy Buckland)
Organization: Research Triangle Institute, RTP, NC
Lines: 45

I have been having a wierd problem with the new LSP 2.0 and since it's 11:00 PM
I can't call THINK tech support, so I thought I'd ask the net. When ever I run
a program within LSP, instead of creating an application and running it outside
of LSP, and that program ends with either a call to ExitToShell or by running 
off the end of the main program or by picking RESET from the RUN menu, my
machine crashes. To try to track down the problem, I used a locked copy of
an original apple system disk (very old and should be virus free if anything 
is) and booted it. I loaded the compiler and the runtime and interface 
libraries onto an newly initialized disk and started the compiler.
I loaded the libraries and created the following main program.

program test;
begin
end.

I added it to the project and compiled it. When I single stepped the program
and executed the last statement, the machine crashes. 

When running on my hard disk with macsbug, I drop into macsbug with the
following instruction being executed:

	movea.l (a2),a2

where a2 = $ffffffff and other bad memory writes must have occured because if I
don't reboot immediately, but just exittoshell, I start to get all kinds of 
random errors.

Since I haven't seen this problem described yet, I would assume that I have a
corrupted copy of the compiler or libraries since this would be too big a bug
to have gone unnoticed. My hardware configuration is as follows.

Mac II
2MB memory
50MB hard disk
2 floppy drives
Apple color card
System software 5.0
SUM inits
MacsBug

-- 
					Randy Buckland (919)-541-7103
					Research Triangle Institute
					rcb@rti.rti.org [128.109.139.2]
					...!decvax!mcnc!rti!rcb