Xref: utzoo comp.sys.mac.programmer:10057 comp.sys.mac.hypercard:2652
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!iconsys!tom
From: tom@iconsys.UUCP (Tom Kimpton)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac.hypercard
Subject: Re: Debugging XFCN's/XCMD's
Message-ID: <412@iconsys.UUCP>
Date: 30 Oct 89 22:45:19 GMT
References: <5870@tank.uchicago.edu>
Reply-To: tom@iconsys.UUCP (Tom Kimpton)
Organization: ICON International, Inc., Orem, UT
Lines: 30

In article <5870@tank.uchicago.edu> gft_robert@gsbacd.uchicago.edu writes:
>
>As a last resort, how would one go about debugging it from the machine level
>(MacsBug, etc.).  I ask, because I'm not sure about the low-level interaction
>between my XFCN and HyperCard itself, and want to know what I should expect to
>be seeing.
>

Not knowing what's available in Pascal, here's what I do in C:
(I hope you know C :-)

{
char dbug[256];
dbug[0] = sprintf(&dbug[1],"formatting and debug info",args);
DebugStr(dbug);
}

Putting this into your code will drop you into the machine level
debugger, with the string being printed out.  Again not knowing
Pascal, but XCFN/XCMD's compiled with the MacsBug symbols option
(LSC&TC) on will retain their symbols when installed in hypercard
and MacsBug will show symbolic offsets.

Hope this helps.

-- 
Tom Kimpton                    UUCP: {uunet,caeco,nrc-ut}!iconsys!tom
Software Engineer	       INTERNET: tom@iconsys.uu.net
Icon International, Inc.       BITNET: icon%byuadam.bitnet (multi-user acct)
Orem, Utah 84058               PHONE: (801) 225-6888