Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!snorkelwacker.mit.edu!stanford.edu!agate!ocf!rgm
From: rgm@ocf.berkeley.edu (Rob Menke)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Debugging MPW Tools
Message-ID: <RGM.91May14012543@avalanche.Berkeley.EDU>
Date: 14 May 91 09:25:43 GMT
References: <ROBERTK.91May13091846@lotatg.lotus.com> <5252@cernvax.cern.ch>
Sender: root@agate.berkeley.edu (Charlie Root)
Distribution: comp
Organization: TEAM CS -- Making Tomorrow's Mistakes Today!
Lines: 32
In-Reply-To: hve@cernvax.cern.ch's message of 13 May 91 14: 37:53 GMT


In article <5252@cernvax.cern.ch> hve@cernvax.cern.ch (H.v.Eicken) writes:

   It would be very helpful if a SADE guru could post a sample
   debugging session...

		      Horst von Eicken, hve@cernvax.cern.ch

I'm not a SADE guru but I play one on USENET!

Seriously, I managed to get SADE to debug a tool by trial-and-error
(mostly the latter).  So, assuming that your tool was compiled and
linked with '-sym on':

     1)	Start up SADE and MPW Shell.
     2) In SADE, type:
	target 'Your:MPW:path:MPW Shell' using 'Your:SYM_file:path:tool.SYM'
     3) Then type:
	SourcePath add 'Your:Source:path:'
     4) Place your breakpoints as usual.
     5) Switch to MPW Shell.  The shell might be acting funny, e.g.
	the cursor might be greyed, selections might be outlined.
	Ignore this.
     6) Execute your tool.  You CANNOT execute any other tools between
	setting up SADE and switching to MPW Shell (SADE 1.1 release
	notes, p. 3).
     7) Find out the bug you have been trying to track down for the
	last six hours resulted from typing '=' when you meant '=='.
--
"Gadget, love, do ya always carry a	|  Robert Menke
 glass cutter?"				|    rgm@OCF.berkeley.edu
"No-- only when I want to cut glass."	|    ...!ucbvax!OCF!rgm