Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LSC 3.0 Questions/Comments
Keywords: LSC 3.0
Message-ID: <28904@ucbvax.BERKELEY.EDU>
Date: 26 Apr 89 03:52:38 GMT
References: <13630@steinmetz.ge.com> <1680@husc6.harvard.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 20

In article <13630@steinmetz.ge.com> leue@crd.ge.com writes:
>1. Is there any way to get a text assembler listing of the code that is
>generated?  I would like to use the LSC code as a starting point for

Macsbug 6.0 has a "log" command for logging sessions, including
disassemblies, to disk.

>2. Is there a better way to examine structs in the debugger?  I find
>the data window pretty klunky compared to, say, Sun's DBXTool. If you're
>trying to follow a linked list of structs, you have to keep opening and
>closing individual data windows, and it takes about 4 steps to view
>each new struct.  Perhaps I'm missing something obvious.

You don't need to close the struct data window, and you don't need to go
back to the main data window.  Just double click in the righthand side of
the field you want to follow.

--- David Phillip Oster            --"When we replace the mouse with a pen,
Arpa: oster@dewey.soe.berkeley.edu --3 button mouse fans will need saxophone
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu --lessons." - Gasee