[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] [Chicken-bugs] #436: Segmentation fault on procedure
From: |
Chicken Scheme |
Subject: |
[Chicken-janitors] [Chicken-bugs] #436: Segmentation fault on procedure with apply |
Date: |
Thu, 29 May 2008 20:41:28 -0000 |
#436: Segmentation fault on procedure with apply
----------------------------------------------+-----------------------------
Reporter: Owen Arden <address@hidden> | Type: defect
Status: new | Priority: minor
Milestone: | Component: compiler
Version: | Keywords: segfault apply
apply-hack
----------------------------------------------+-----------------------------
When defining a procedure using a lambda with an improper argument list
with five or more required arguments, then passing those arguments to
apply, I get strange behavior including segmentation faults when this
procedure is called incorrectly. Below is an example:
{{{
(define foo
(lambda (a b c d e . f)
(apply list a b c d e f)))
}}}
If I call this procedure with the wrong number of arguments, such as in:
{{{
(foo 1)
}}}
I get a segfault on chicken 3.1.0 built on 32-bit and 64-bit Gentoo Linux
boxes. I also get this same behavior on chicken 2.732 (only tested on 64-
bit).
Is this an apply-hack problem?
--
Ticket URL: <http://trac.callcc.org/ticket/436>
Chicken Scheme <http://www.call-with-current-continuation.org/>
The CHICKEN Scheme-to-C compiler
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-janitors] [Chicken-bugs] #436: Segmentation fault on procedure with apply,
Chicken Scheme <=