Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!wuarchive!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Monitor trap
Message-ID: <2719@husc6.harvard.edu>
Date: 28 Sep 89 13:29:33 GMT
References: <1363@majestix.ida.liu.se>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 28

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?

	Debugger() or DebugStr() will do the trick; when under the source
debugger, the pass control to the source debugger, but when running standalone,
they wil enter TMON or MacsBug (whichever you have installed).

	You might also try a TRAP $F, which TMON will  intercept, but I don't
know about MacsBug.

R.

~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"There is no personal problem which cannot be solved by sufficient
application of high explosives."

~~~~~~~~~~~~~~~