[Gc] Fwd: Re: Stack overflows, Ex: bdwgc SIGSEGV when stack size is exeeded
2014-04-12 07:33:04 GMT
-------- Forwarded message --------
From: oops <at> posteo.de
To: Ivan Maidanski <ivmai <at> mail.ru>
Date: Thu, 10 Apr 2014 18:11:15 +0200
Subject: Re: Fwd: [Gc] Stack overflows, Ex: bdwgc SIGSEGV when stack size is exeeded
> -------- Forwarded message --------
> From: Ingo Albrecht <prom <at> opendylan.org>
> To: bdwgc <at> lists.opendylan.org
> Date: Thu, 10 Apr 2014, 01:18 +04:00
> Subject: [Gc] Stack overflows, Ex: bdwgc SIGSEGV when stack size is
> On 04/09/2014 01:12 PM, Ivan Maidanski wrote:
> > I am wondering if there is by any chances a way for a soft(er)
> > if the stack space is exhausted? I believe the cause to be in the
> > size, since setting a ulimit -s changes the point in time when the
> > program crashes. The program is an interpreter and is given a
> > definition - so it is expected that something bad happens; I am
> > trying to figure out what my options are to not crash to hard or at
> > least print a diagnostic message or something.
> > I'd apprechiate any comments you may have.
> It might be possible to use protocols from libraries like this one:
> AFAIK, this library has been created for CLISP.
> I've had some good experience with it in (non-GC) C++ projects.
> Currently, it probably collides with BDWGC signal handling or might
> be dependent on a specific initialization order. But it might be
> possible to figure out how to use it with BDWGC portably.
> bdwgc mailing list
> bdwgc <at> lists.opendylan.org
Thanks. Much appreciated and I'll look at the things you suggested.
Perhaps this is an idea for a future development. Being able to set a
max stack size and have the GC return gracefully if it tries to exceed
that limit. But I should also mention that the GC is very useful! Also
thanks for the mailing list, I was not aware of it.
_______________________________________________ bdwgc mailing list bdwgc@... https://lists.opendylan.org/mailman/listinfo/bdwgc