|
![](/i/fill.gif) |
> clipka <ano### [at] anonymous org> wrote:
>> Am 13.10.2012 17:44, schrieb Anthony D. Baye:
>>
>>> at any rate, it would probably be a good idea to do some error checking on the
>>> stack size before it overflows and causes a segfault.
>>
>> We'll implement such a check as soon as we've figured a way to solve the
>> halting problem :-P
>
> Funny. Really.
>
> I had assumed that the stack in question was not the system stack. i.e. part of
> the code... And that it had a known max size.
>
> Even if this is not the case, it should still be possible to implement some kind
> of check to prevent a segfault.
>
> But, again, I am not familiar with the code.
>
> Regards,
> A.D.B.
>
>
Checking for an impeding stack overflow is always tricky, whatever the
stack implementation. Having a static stack size don't mean that you can
acurately detect when an overflow could appen.
Also, such a check will slow down ALL accesses to the stack, possibly
severly.
Post a reply to this message
|
![](/i/fill.gif) |