Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!kksys!edgar!mmug!p510.f22.n282.z1.mmug.edgar.mn.org!jspencer
From: jspencer@p510.f22.n282.z1.mmug.edgar.mn.org (Jim Spencer)
Newsgroups: comp.sys.mac.programmer
Subject: Debugging Stand-Alone Code Resources
Message-ID: <1.27C5B494@mmug.edgar.mn.org>
Date: 22 Feb 91 23:29:25 GMT
Sender: ufgate@mmug.edgar.mn.org (newsout1.26)
Organization: FidoNet node 1:282/22.510 - SmorgasBoard, Twin Cities
Lines: 21


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 because of the way they are copied before being run.

I don't see anyway to debug stand-alones of any type in Think Pascal's debugger as, by definition these need to be compiled in a project seperate from the program being run in the debugger.
 

--  

                   Jim Spencer (jspencer@mmug.edgar.mn.org)
               UUCP: ...jhereg!tcnet!vware!edgar!mmug!jspencer
                             FidoNet: 1:282/22.510

--