Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!mcsun!cernvax!chx400!chx400!bernina!neptune!c!mneerach
From: mneerach@iiic.ethz.ch (Matthias Ulrich Neeracher)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Debugging Stand-Alone Code Resources
Message-ID: <26200@neptune.inf.ethz.ch>
Date: 24 Feb 91 10:45:51 GMT
References: <1.27C5B494@mmug.edgar.mn.org>
Sender: news@neptune.inf.ethz.ch
Reply-To: mneerach@iiic.ethz.ch
Organization: Departement Informatik, ETH, Zurich
Lines: 25

In article <1.27C5B494@mmug.edgar.mn.org>, jspencer@p510.f22.n282.z1.mmug.edgar.mn.org (Jim Spencer) writes:
>
>Robert Murphy writes in a message to All
>
>RM> To round out this document, I would like to know what, if any, 
>RM> support for debugging stand-alone code resources is provided 
>RM> by SADE and by the Think source debuggers. As close as I can 
>RM> see from reading their documentation, it doesn't look like any, 
>RM> but I might have missed something. 
>
>While I haven't tried it myself, SADE is supposed to be able to debug
>stand-alone resources the same way that it debugs application code: you do your
>builds with -sym on and identify the source files explicitly to the debugger.  
>The exception is XCMD's be cause of the way they are copied before being run.

If somebody has managed to debug a 'cdev' resource with SADE without blowing
up the system, please let me know. (But then, I haven't tried it for a year,
maybe it works with the new & improved SADE)

Matthias

-- 
Matthias Neeracher                                   mneerach@iiic.ethz.ch
   "These days, though, you have to be pretty technical before you can 
    even aspire to crudeness." -- William Gibson, _Johnny Mnemonic_