guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A stack overflow problem.


From: Mark H Weaver
Subject: Re: A stack overflow problem.
Date: Fri, 06 Dec 2013 10:58:07 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Mark H Weaver <address@hidden> writes:

> I think we need two different stack reserves: one that's used normally,
> and another smaller one that's used within the debugger after a stack
> overflow.  It should be possible to do some minor debugging after a
> stack overflow: enough to see where the overflow happened and maybe look
> at some stack frames to investigate why it happened.  The normal stack
> reserve should be reinstated after leaving the debugger.

Another option is to run the debugger in a freshly allocated stack.  I
think this is probably the best solution, but I don't know how hard it
would be to do.  I know very little about our debugger implementation.

     Mark



reply via email to

[Prev in Thread] Current Thread [Next in Thread]