Path: utzoo!attcan!uunet!munnari!murtoa.cs.mu.oz.au!munnari.oz!jkjl
From: jkjl@munnari.oz (John Lim)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Debugging code resources with SADE...?
Keywords: How to do it..?
Message-ID: <1525@murtoa.cs.mu.oz.au>
Date: 24 May 89 04:55:02 GMT
References: <998@acf3.UUCP>
Sender: news@cs.mu.oz.au
Reply-To: jkjl@munmurra.UUCP (John Lim)
Organization: University of Melbourne, Comp Sci Dept
Lines: 33

In article <998@acf3.UUCP> spector@acf3.UUCP (David HM Spector) writes:
>
>I think that someone prbably posted the answer to this just a few days
>ago, but I cannot seem to find it anywhere... sooo...
>
>Can anyone tell me a way to get SADE to debug standalone code
>resources such as CDEVs? 

This is not an answer to your question but a comment.

I tried to make a 'cdev main.c' file for LSC 3.0 so that i could
debug the Moire cdev using LSD. What happened was a lot of scrunches
and crunches - and lots of rebooting :-).

The control panel does *funny* things with the resource file list. It
saves and then removes all resource maps that the current application
has opened and then inserts the resource map of the current cdev
into the resource file list when a cdev event occurs. 

Then after a cdev event is processed the resource maps of the application
are restored and the resource map of the current cdev removed. Presumably
this is to reduce resource type/id conflicts.

I tried to patch around it once. I gave up after it failed. It would
take too much time disassembling the Control Panel and understanding
how LSD handles resources to make it worthwhile.

Perhaps someone at THINK has implemented what i attempted ?

	john lim

Note : LSC allows you to debug DAs by making the DA think it is an application.
I was trying to do the same, making my cdev think it was an application.