HyperCard: How to Debug "Too Much Recursion" Error Message


A user is having a "too much recursion" problem in a HyperCard stack
that he is developing. The error occurs during a callback into HyperCard
from an XCMD, which he wrote. He has checked his code for problems. Is
there a way to determine what triggers the "too much recursion" message
(like a traceback)?

We are not aware of any trace-back facilities available for HyperCard.
HyperCard, itself, does not have the type of tracing needed here. Further,
we could not locate any third-party add-ons available to resolve this
problem.

To debug a problem of this sort, put information from the scripts and XCMDs
you are using into debugging fields. This information usually includes a
line per handler or XCMD call that includes the parameters being passed.
When the recursion problem occurs, you then can inspect the trace that you
have effectively created.


Published Date: Feb 18, 2012