[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stack overflow
From: |
Ludovic Courtès |
Subject: |
Re: stack overflow |
Date: |
Thu, 14 Feb 2008 12:25:20 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
Hi,
"Mikael Djurfeldt" <address@hidden> writes:
> I think you should measure the effect on performance. Even if the hit
> isn't dramatic, remember that many a little makes a mickle...
Indeed...
> Speaking as a user, I would prefer a solution where the evaluator
> measures stack size the same way as currently (i.e. without the need
> to do extra work at every return). It is possible to estimate the
> average sizes of evaluator stack frames during startup and use this as
> a conversion factor in the debug-options interface (scm_debug_opts) so
> that the user setting is approximately consistent between platforms.
Hmm, I don't see how we could reliably estimate this, and I'm afraid it
would add non-determinism (e.g., estimate that varies with the phase of
moon, dubious estimates, loads of users suddenly reporting stack
overflows because Fedora Core now ships with a bleeding-edge compiler
noone else uses, etc.).
That said, I agree that an overhead-free solution similar to the current
one is preferable.
Thanks,
Ludovic.
Re: stack overflow, Han-Wen Nienhuys, 2008/02/16