Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!usc!samsung!rex!mandel@vax.anes.tulane.edu
From: mandel@vax.anes.tulane.edu (Jeff E Mandel MD MS)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Debugging Stand-Alone Code Resources
Message-ID: <6154@rex.cs.tulane.edu>
Date: 14 Feb 91 20:42:03 GMT
References: <2725@autodesk.COM>
Sender: news@rex.cs.tulane.edu
Organization: Tulane University School of Medicine
Lines: 17

In article <2725@autodesk.COM> bobert@Autodesk.COM (Robert Murphy) writes:
>I am writing a technical document describing how to build and debug a
>certain type of stand-alone code resource.  I know that Macsbug, TMON,
>and Jasik's Debugger provide some level of support for stand-alone
>code resources, and in fact have used Jasik to debug the example code.
>To round out this document, I would like to know what, if any, support
>for debugging stand-alone code resources is provided by SADE and by
>the Think source debuggers.  As close as I can see from reading their
>documentation, it doesn't look like any, but I might have missed something.

I have used SADE to debug LDEFs. It is reasonably straightforward; just set the
target and source files explicitly.

Jeff E Mandel MD MS
Asst Professor of Anesthesiology
Tulane University School of Medicine
New Orleans, LA