[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] segfault in chicken
From: |
F. Wittenberger |
Subject: |
Re: [Chicken-users] segfault in chicken |
Date: |
Sun, 21 Mar 2010 22:31:59 +0100 |
sorry,
probably my fault. I did not check that the code I posted will
reproduce the issue. All I verified was that just this fix was all to
compile my project again. The conditions are not comparable:
compilation, cond-expand, include, export/import all around between the
error source (file A) and the segfault on reference in file B.
I'll be back if I have a reproducible case.
Am Sonntag, den 21.03.2010, 13:30 -0400 schrieb Mario Domenech Goulart:
> On Sat, 20 Mar 2010 12:14:59 +0100 Jörg "F. Wittenberger" <address@hidden>
> wrote:
>
> > I just made a cut&paste mistake. Now I feel chicken could do better
> > than segfault at this:
> >
> > (define-syntax pass-a-ref
> > (define-syntax with-a-ref
> > (syntax-rules ()
> > ((_ ref b) b)))
> > (syntax-rules ()
> > ((pass-a-ref ref b name)
> > (let ((t (make-thread (lambda () b) name)))
> > (thread-start! t)
> > (delay (thread-join! t))))))
>
> I can't reproduce the problem just by evaluating the code above. Is
> there anything I should do to trigger the segfault?
>
> 4.2.0 and 4.3.0 report the following error: