🚀 go-pugleaf

In article <808@jumbo.dec.com> brooks@jumbo.UUCP (Ken Brooks) writes:
>
>I'm using Lightspeed C, and I'm happy with all of it except the
>debugging.  Macsbug is just too low-level.  In particular, I really
>wish I had symbols for variables (globals at least!) and some level of
>coordination with the source.  Are there any debuggers out there,
>compatible with LSC, that provide this?  Or that in other ways improve
>upon Macsbug?  What do people recommend, and where can I get it?
>
>Incidentally, I just converted to version 2.0 of Lightspeed C, and now
>Macsbug (the Maxbug version) doesn't see any symbols at all!  I
>carefully made sure that the "Macsbug symbols" option was checked, and
>recompiled everything.  No help.  Does anyone recognize the problem, or
>know a solution?
>
>Ken Brooks

I'm using TMON, which does quite a good job of debugging.  Being able to
open several windows into disassembly, memory locations makes it really
worth the while.

If you have one of the latest user areas, and you have Steve Jasik's Nosy,
you can generate procedure names for TMON.  Just Nosy the file until you're
satisfied, then save a .map file (on the closing dialog box) and then
read in the .map file after saving some space for labels in the user area of
TMON.  This came in quite handy for me when I was trying to reposition some
text for pre-printed forms in an accounting program.

You also might want to make sure you have the latest version of Macsbug
(I think it's version 5.0, but I may be wrong).

Good luck,
Owen


Owen Hartnett
Brown University Computer Science

omh@cs.brown.edu.CSNET 
omh%cs.brown.edu@relay.cs.net-relay.ARPA
{ihnp4,allegra}!brunix!omh