Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!mordor!sri-spam!ames!pasteur!ucbvax!POLYA.STANFORD.EDU!lipa
From: lipa@POLYA.STANFORD.EDU (William Lipa)
Newsgroups: comp.sys.mac.programmer
Subject: Is there a bug in LSP when running in color?
Message-ID: <8804261843.AA02822@polya.stanford.edu>
Date: 26 Apr 88 18:43:50 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 28

I have a program written in LSP which causes a system error or the "flashing"
empty dialog box when it transfers control back to LSP after finishing. It
appears as though the program is trashing some structure necessary for LSP, but
I can't imagine how it would do this, since the program doesn't do any funny
pointer manipulation and all memory is allocated by standard toolbox calls.
I know there is a great tendency to blame the compiler; I was just wondering
whether there was a known bug in LSP that could cause this behavior.

Reasons I believe it might be LSP, not my code:
  1. The program never bombs when it is running as an application.
  2. No errors are caught by LSP when it is running in Debug mode.
  3. The program never causes neighboring programs to bomb while running in
     MultiFinder, so it doesn't seem to be randomly trashing memory.
  4. The problem goes away if I use a Mac Plus or if I turn off the color on
     my Mac II. My program does not use color.
  5. The problem does not go away if I increase the heap and stack size of my
     program, so it's not a simple memory error.

System configuration: Mac II, Apple color monitor, System release 5.0, regular
     Finder, 16-color mode, 40SC disk, LightSpeed Pascal 1.11.

Even if nobody has ever heard of anything like this, I would be very interested
to see a list of known bugs in LSP since I do a lot of development with it (and
like it!)

Thanks,

Bill Lipa
lipa%polya@forsythe.stanford.edu