On Dec 3 2018, Peter Bex wrote:
On Mon, Dec 03, 2018 at 10:46:38AM +0100, Jörg F. Wittenberger wrote:
So for me the question remains: wouldn't it be much, much more
efficient to work sort-of hand-in-hand with one of the core developers,
or maybe on the list to get the remaining things (bugs
On Mon, Dec 03, 2018 at 10:46:38AM +0100, Jörg F. Wittenberger wrote:
> Whats going on here IMHO is that a lot of lifetime, your guys and mine, is
> wasted. At the same time the code quality of the result is likely worse that
> what I'm using as the source to cut out those patches. [...]
>
> So
Thanks you so much Kon,
reviewing these logs helped to confirm my feelings.
Feelings, not findings. Yet.
Tinkering with these scheduler/srfi-18 issues again really made me feel bad
and sorry. In fact the anger has cost me the sleep of the better half of
the night. Still enrages me.
Whats
Thanks for the replies,
chicken-install -r srfi-18 ; did the trick already
I should have stated that that's what I have, what I've been looking for
was the git history. I wonder for some statements why the hell they are
there at all. Two possible reasons: a) I cleaned them up for being
well, that shows me. ;-)
trying to track down why
#497 $ chicken-install -r srfi-18
mapped (srfi-18) to ()
retrieving ...
> On Dec 2, 2018, at 10:42 AM, Kon Lovett wrote:
>
> C5 evicted srfi-18, along w/ srfi-1, 13, 14, & 69, to the egg store.
>
> chicken-install -retrieve.
>
>> On Dec 2,
C5 evicted srfi-18, along w/ srfi-1, 13, 14, & 69, to the egg store.
chicken-install -retrieve.
> On Dec 2, 2018, at 10:39 AM, Jörg F. Wittenberger
> wrote:
>
> Hi all,
>
> when I tried to reply in a timely manner I apparently sent out a link to a
> broken file. Sorry for that.
>
> Just
Hi all,
when I tried to reply in a timely manner I apparently sent out a link to a
broken file. Sorry for that.
Just wanted to see if I could create a patch for the current master.
For this I need srfi-18 egg source too. Just I can't find it.
Jöry
On Nov 30 2018, Jörg F. Wittenberger
Hello Megane,
On Nov 30 2018, megane wrote:
Hi,
Here's another version that crashes quickly with "very high
probability".
...
24 Error: (mutex-unlock) Internal scheduler error: unknown thread state
25 #
26 ready
This bears an uncanny resemblance to scheduler issues I've
Hi,
Here's another version that crashes quickly with "very high
probability".
(cond-expand
(chicken-5 (import (chicken base))
(import (chicken time))
(import srfi-18))
(else (import chicken)
(use srfi-18)))
(define m (make-mutex))
(print "@@ " (current-thread)
