Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!decwrl!ucbvax!tut.cis.ohio-state.edu!ukma!psuvm.bitnet!cunyvm!nyser!cmx!rodan.acs.syr.edu!pcossenb From: pcossenb@rodan.acs.syr.edu (Paul C. Ossenbruggen) Newsgroups: comp.sys.mac.programmer Subject: Re: symbol tables for LSC, code resources and TMON Message-ID: <1589@cmx.npac.syr.edu> Date: 25 May 89 03:30:15 GMT References: <2115@ur-cc.UUCP> Sender: usenet@cmx.npac.syr.edu Reply-To: pcossenb@rodan.acs.syr.edu Organization: Syracuse University, Syracuse, New York Lines: 28 In article ksitze@nmsu.edu (Kevin Sitze) writes: >In article: 18:06:04 GMT> Eric writes: >>>that it would be nice if I could see what procedure I was debugging. >> >I'm afraid that LSC doesn't generate a symbole table (as far as I >know) but you can get the information you want by going into the >options dialog box (in the Edit menu, at the very bottom). Click on >the option 'Code Generation' and select the first choice: 'MacsBugs >symbols'. TMON will display the first eight characters (in uppercase) >of the current routine. No problem. > Just remeber that TMON will not see the procedure unless the procedure sets up a stack frame. That is, in assembly, uses the Link instruction. So procedures without any parameters or local variables will not show up. - Paul ------------------------------------------------------------------------------- | Paul C. Ossenbruggen pcossenb@rodan.acs.syr.edu | | Syracuse University rspco@suvm.bitnet | | pcossenb@sunrise.acs.syr.edu |