Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!agate!ucbvax!pasteur!anableps.berkeley.edu!korn
From: korn@anableps.berkeley.edu (Peter "Arrgh" Korn)
Newsgroups: comp.sys.mac.programmer
Subject: Question on using SADE to debug 'cdev's and 'DRVR's
Message-ID: <19293@pasteur.Berkeley.EDU>
Date: 8 Nov 89 07:38:29 GMT
References: <28633.2555C882@cmhgate.FIDONET.ORG>
Sender: news@pasteur.Berkeley.EDU
Reply-To: korn@anableps.berkeley.edu (Peter "Arrgh" Korn)
Organization: What, me organized???
Lines: 24

I would like to use SADE to debug a cdev that I'm writing.  I initially 
wrote the cdev under Think C, but for a variety of reasons (not the least
of which is that the Think C debugger constantly crashes when debugging
my cdev), I'm moving over to MPW C.  I will also later be writing a DRVR
in MPW C.  I would like to use the SADE debugger on both the cdev and DRVR.

Trying the obvious 'target "rootVol:system folder:DA Handler" using "..."'
doesn't work; SADE will only target APPLs.  My basic understanding of
how SADE does it's debugging is: it needs to get a valid MultiFinder process
to target, and then will debug anything in that processes resource map
(as it does with MPW tools).  Therefore I would assume that some sort of
cdev-shell program would work (as well as a DRVR-shell).

Is this correct?  If so, does a cdev-shell program exist?  A DRVR-shell?
Is there anyway to just walk through the MultiFinder process list, break
the DA Handler, and go from there?  Or perhaps open the Control Panel inside
an application's layer and go from there?


Peter
--
Peter "Arrgh" Korn
korn@mica.Berkeley.EDU
{decvax,hplabs,sdcsvax,ulysses,usenix}!ucbvax!mica!korn