CHICKEN Scheme

Metadata

Id: 616a19e6f7aa222ac353693249c92c253eb55617
Trac id: 1199
Type: defect
Reporter: kooda
Owner:
Cc:
Status: closed
Component: unknown
Estimated difficulty:
Resolution: fixed
Priority: major
Milestone: 4.11.0
Version: 4.10.x
Changetime: 2015-09-05 17:32:20 UTC
Created: 2015-07-06 01:01:33 UTC
Keywords:

Description

While trying out the latest release candidate of CHICKEN (4.10.0rc2) on my NetBSD machine, I stumbled upon that error when performing `make check`:

 ======================================== lolevel tests ...
 
 Error: assertion failed: (equal? (quote (hello 1 2)) (foo 1 2))
 
         Call history:
 
         <eval>    (eq? foo new-foo)
         <syntax>          (assert (equal? (quote (hello 1 2)) (foo 1 2)))
         <syntax>          (##core#let ((tmp154 (equal? (quote (hello 1 2)) (foo 1 2)))) (##core#if (##core#check tmp154) tmp15......
         <syntax>          (##core#begin (##core#if (##core#check tmp154) tmp154 (##sys#error "assertion failed" (##core#quote ...
         <syntax>          (##core#if (##core#check tmp154) tmp154 (##sys#error "assertion failed" (##core#quote (equal? (quote......
         <syntax>          (##core#check tmp154)
         <syntax>          (##sys#error "assertion failed" (##core#quote (equal? (quote (hello 1 2)) (foo 1 2))))
         <syntax>          (##core#quote (equal? (quote (hello 1 2)) (foo 1 2)))
         <syntax>          (equal? (quote (hello 1 2)) (foo 1 2))
         <syntax>          (quote (hello 1 2))
         <syntax>          (##core#quote (hello 1 2))
         <syntax>          (foo 1 2)
         <eval>    (equal? (quote (hello 1 2)) (foo 1 2))
         <eval>    (foo 1 2)
         <eval>    [foo] (list a b)
         <eval>    (##sys#error "assertion failed" (##core#quote (equal? (quote (hello 1 2)) (foo 1 2))))        <--
 rules.make:658: recipe for target 'check' failed
 gmake: *** [check] Error 70

I then tried to run a git bisect to pinpoint when this error appeared for the first time (I ran the bisect with a fresh bootstrap each time). It led me to the following commit: **a3b8a0adf77a9a7ec65a66918a84c2bbda0f97cc**

Please let me know if you need any more details and further testing. I’ll try to investigate as well.

Changes and comments

[2015-07-06 02:36:07 UTC] kooda wrote:

The test doesn’t fail with clang 3.5.0 on the same platform. The previous (failing) result was using gcc 4.8.4 for x86.

[2015-07-28 14:20:43 UTC] kooda wrote:

I just tested 4.10.0rc4 with my system upgraded, with gcc 4.8.5, I get the exact same error.

I also tried the argvector branch and all checks pass without error.

[2015-08-27 08:53:19 UTC] sjamaan changed milestone from 4.10.0 to 4.11.0

[2015-08-27 08:53:19 UTC] sjamaan wrote:

I'm guessing argvector may fix this, then. Let's keep it open for 4.11 (argvector hasn't been merged yet)

[2015-09-05 17:32:20 UTC] sjamaan changed status from new to closed

[2015-09-05 17:32:20 UTC] sjamaan set resolution to fixed

[2015-09-05 17:32:20 UTC] sjamaan wrote:

argvector has now been merged

Summary