Thanks for the ideas.
Actually what I did was running script
and then turning on tracing in the debugger.
Then I looked at the result to find out where exactly was the
recursion called.
thanks
Gabor
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Matthew O. Persico) writes:
>On 11 Jan 2004 17:33:32 -, Peter Scott wrote:
>> In article <[EMAIL PROTECTED]>,
>> [EMAIL PROTECTED] (Gabor Szabo) writes:
>>>
>>> Any idea how can I use the debugger to find the cause of
>>> a deep recursion in m
Set a break-point on the sub that is recursing; step through it, paying
attention to the value(s) of the variable(s) that are passed across the
argument-list interface.
B
Gabor Szabo wrote:
Any idea how can I use the debugger to find the cause of
a deep recursion in my code ?
Gabor
On 11 Jan 2004 17:33:32 -, Peter Scott wrote:
> In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] (Gabor Szabo) writes:
>>
>> Any idea how can I use the debugger to find the cause of
>> a deep recursion in my code ?
>
> I don't see the need for the debugger. Deep recursion is a
> warning, so
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Gabor Szabo) writes:
>
>Any idea how can I use the debugger to find the cause of
>a deep recursion in my code ?
I don't see the need for the debugger. Deep recursion is a warning, so
just turn the warning into a fatal error with stack trace:
%
Any idea how can I use the debugger to find the cause of
a deep recursion in my code ?
Gabor
