[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #975: Segmentation fault when accessing/setting m
|
From: |
Chicken Trac |
|
Subject: |
Re: [Chicken-janitors] #975: Segmentation fault when accessing/setting moderately large SRFI-4 vectors |
|
Date: |
Tue, 05 Feb 2013 01:20:50 -0000 |
#975: Segmentation fault when accessing/setting moderately large SRFI-4 vectors
-----------------------+----------------------------------------------------
Reporter: iraikov | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 4.9.0
Component: compiler | Version: 4.8.x
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment(by iraikov):
Running the program under gdb reveals that the segmentation fault is
caused by stack overflow.
It appears that if gcc is passed option -O2 or -O3, the program terminates
normally, regardless of csc optimization flags. Is it possible that
Chicken-generated code relies on tail-call elimination performed by gcc?
--
Ticket URL: <http://bugs.call-cc.org/ticket/975#comment:3>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.