2008/10/6 Ludovic Courtès <[EMAIL PROTECTED]>:
> Hello,
>
> Sorry for the latency...
Hi, no problem!
> "Neil Jerram" <[EMAIL PROTECTED]> writes:
>
>> - The problem we actually need to solve is getting a stack overflow
>> while running make and/or make check, and there may be other ways of
>> doing that than trying to pick the right number, and to interpret that
>> number such that it has the same effect on all platforms.
>
> You mean "is *not* getting a stack overflow", right?
Well, the problem is getting a stack overflow; the objective is *not*
to get one. :-)
> >From that point of view, adding the right `eval-set!' incantation
> somewhere in the test suite would suffice to fix the problem.
Yes - except that it's (debug-set! stack ...).
>> - Based on [2], it sounds like there is part of this issue that we
>> don't yet understand - i.e. not just the stack growing bigger than the
>> default 20000 words.
>
> What makes you say so? The message just shows that the test suite
> sometimes triggers a stack overflow.
Yes, but the point is that in that case, the calibration patch makes
things worse! (And I've now followed up in more detail in that
thread.)
> Thanks,
> Ludo'.
Regards,
Neil
