Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!ksand
From: ksand@Apple.COM (Kent Sandvik)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Debugging Stand-Alone Code Resources
Message-ID: <49229@apple.Apple.COM>
Date: 15 Feb 91 23:40:38 GMT
References: <2725@autodesk.COM> <6154@rex.cs.tulane.edu>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 28

In article <6154@rex.cs.tulane.edu> mandel@vax.anes.tulane.edu (Jeff E Mandel MD MS) writes:
>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.

...just some comments, do not make the CODE resources to float in 
memory, so SADE will have hard times to find the standalone code segment.
Also, copying CODE segments to other handles so SADE don't find the
entrypoints is also bad.

regards,
Kent


-- 
Kent Sandvik, Apple Computer Inc, Developer Technical Support
NET:ksand@apple.com, AppleLink: KSAND  DISCLAIMER: Private mumbo-jumbo
Zippy++ says: "C++ is a write-only language, I can write programs in C++
but I can't read any of them".