Opened 10 years ago
Closed 10 years ago
#1199 closed defect (fixed)
lolevel check error on NetBSD
| Reported by: | Kooda | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 4.11.0 |
| Component: | unknown | Version: | 4.10.x |
| Keywords: | Cc: | ||
| Estimated difficulty: |
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.
Change History (4)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
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.
comment:3 by , 10 years ago
| Milestone: | 4.10.0 → 4.11.0 |
|---|
I'm guessing argvector may fix this, then. Let's keep it open for 4.11 (argvector hasn't been merged yet)

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.