[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #876: csi segfaults immediately when running this
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #876: csi segfaults immediately when running this code |
Date: |
Mon, 02 Jul 2012 09:08:50 -0000 |
#876: csi segfaults immediately when running this code
-------------------------+--------------------------------------------------
Reporter: ckeen | Owner: felix
Type: defect | Status: assigned
Priority: major | Milestone: 4.8.0
Component: core tools | Version: 4.7.x
Resolution: | Keywords: csi segfault master
-------------------------+--------------------------------------------------
Changes (by felix):
* owner: => felix
* status: new => assigned
Comment:
This is a simple stack overflow. Normally this should not be a problem as
chicken allocates activation frames on the heap, but the checks that test
whether the nursery is full (and whether a minor GC is needed) are not
generated in all compiled procedures - specifically: not in continuation
procedures. As long as these call normal compiled code, the called
procedures will perform the check. Here we have the situation that the
called procedure is a "primitive" (the internal, manually written C code
for `*`), which doesn't do a stack/nursery-check.
Emitting stack-checks in all procedures might be too costly. One option
would be to add stack-checks in primitives, or wrap them in a thunk, or
something. I have to ponder this.
--
Ticket URL: <http://bugs.call-cc.org/ticket/876#comment:3>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Chicken-janitors] #876: csi segfaults immediately when running this code,
Chicken Trac <=