jamesm@sco.COM (James M. Moore) (01/21/89)
In article <24089@cornell.UUCP> wiriyan@svax.cs.cornell.edu (Tjipta Wiriyan) writes: > >How can both LSC 3.0 and its debugger be run on a 1 MB Mac SE? I know it has >been discussed before, but I forgot how it is done. Create a code resoure that contains nothing but this: main () { ExitToShell(); }; Install this as an fkey. Start up LSC, switch layers to the finder, and press the fkey. Finder goes away, and you get that memory back to use the debugger in. I set the LSC partition size to 350K, the debugger to 150-200K, and give my project the rest of the room to work in (about 200K). Be prepared for many "out of memory" error messages in the data window. You'll usually get the message when you're trying to display structs. (Work-around is to just display individual elements of structs). It does seem to display the error message more frequently when the data is on the stack, rather than in global space. (This is just an impression - your mileage may vary). I have had trouble loading in large libraries, such as MacTraps, but my solution was to just create a project with MacTraps, stdio, and several other libraries, compile that in a 700k LSC partition, and then make copies of that project whenever I need to start a project from scratch. If anyone else has any tips for running in this configuration, please let me know. Think support suggested reducing the debugger partition even further, but I haven't had much success with that so far. One thing this configuration definately teaches you is to segment heavily and always check to make sure NewHandle and NewPtr don't return nil. -- ** James Moore ** ** Internet: jamesm@sco.com ** ** uucp: {decvax!microsoft | uunet | ucbvax!ucscc | amd}!sco!jamesm ** ** Nil clu no suim ar bith ag SCO ceard a bhfuil me ag scriobh anois. **
dudek@ai.toronto.edu (Gregory Dudek) (01/24/89)
In the discussion on running the Think LSC debugger on a 1 Meg machine,
you should, of course, also minimize memory usage in any way possible.
Make sure to disable any many INITs as possible and avoid using non-ROM
fonts before running the debugger. Even so, I've had a lot of
trouble using the data window with large projects and use the debugger
simply for tracing execution.
What I'd really like to see is for Symantec to distribute a small
version of LSC itself that could be used just for launching the debugger
and nothing else, hence saving on memory. That can't be too hard, can
it guys?
--
Dept. of Computer Science (vision group) University of Toronto
Nice mailers: dudek@ai.utoronto.ca
UUCP: {uunet,decvax,linus,pyramid,
dalcs,watmath,garfield,ubc-vision,calgary}!utai!dudek
ARPA: user%ai.toronto.edu@relay.cs.net