Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!psuvax1!rutgers!dptg!att!cbnewsk!ech
From: ech@cbnewsk.ATT.COM (ned.horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Monitor trap
Message-ID: <1094@cbnewsk.ATT.COM>
Date: 28 Sep 89 14:52:17 GMT
References: <32890@srcsip.UUCP>
Organization: AT&T Bell Laboratories
Lines: 29

In article <1363@majestix.ida.liu.se> andwi@majestix.ida.liu.se (Andreas Wickberg) writes:

>When working in THINK-C I sometimes get different result (= bombs)
>when running the program from within THINK-C or as a stand alone
>application. I've tried to find a way of calling the monitor (eg.
>Macsbug) from the program to do the debugging from there, but without
>luck. THINK can do this (cmd-M when debuggin), but how?
 
From article <32890@srcsip.UUCP>, by mnkonar@manyjars.SRC.Honeywell.COM (Murat N. Konar):
> There are two calls which should be callable from C.

> In Pascal they are:

> procedure debugger;
> {simply drops you into the debugger}

> procedure debugStr(theStr:str255);
> {drops you into the debugger and displays a string}
> {there.  Very, very handy.}

> These calls are trap based but I can't recall the 
> trap words.

These are known to TC4; spelling is consistent with Inside Mac, i.e.

	Debugger();	/* trap a9ff */
	DebugStr("\PHello Debugger!");	/* abff */

=Ned Horvath=