siegel@endor.harvard.edu (Rich Siegel) (04/24/89)
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 No. You might consider writing assembler from scratch, using the inline assembler. >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 can always type an expression in the data window which would evaluate to the structure at the end of the chain you're following. You'll get a scalar value or a "struct 0x$$$$$$" which you can then double-click on. --Rich ~~~~~~~~~~~~~~~ Rich Siegel Staff Software Developer Symantec Corporation, Language Products Group Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel "She told me to make myself comfortable, so I pulled down my pants and sat in the pudding." -Emo Phillips ~~~~~~~~~~~~~~~
kaufman@polya.Stanford.EDU (Marc T. Kaufman) (04/25/89)
In article <1680@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes: >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 > No. You might consider writing assembler from scratch, using the >inline assembler. Yes. With MacNosy from Jasik Designs. You can get assembly with interspersed source code, so you can see where things came from. Marc Kaufman (kaufman@polya.stanford.edu)
oster@dewey.soe.berkeley.edu (David Phillip Oster) (04/26/89)
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