Search
16:21:52
stassats
|3b|: does it work without https://github.com/slime/slime/commit/5f23adaa88c034449d935b7a0bc26ed936d5ed0e
16:25:02
|3b|
without the wake-thread it works (aside from being slow to notice the interrupt sometimes)
16:25:26
|3b|
testing without the whole change will take a bit, need to check it out from git...just a sec
16:25:30
stassats
sb-thread:condition-wait maybe just broken on windows thne
16:26:37
|3b|
i don't think it is only condition-wait, breaks in with-mutex some of the time, and in condition-wait some of the time
16:27:13
|3b|
i guess it is possible both are broken though
16:27:58
|3b|
well, seems like the interrupts are happening at places they are allowed to
16:28:34
|3b|
and if they should be allowed there, the problem is grabbing the mutex from the interruption
16:28:49
|3b|
no idea if they should be allowed there or not :)
16:37:59
stassats
well, it works on linux and macos, so somethings must be not right on windows
16:38:48
|3b|
yeah, seems OK with that change reverted
16:54:50
stassats
i guess i see, it's precisely because it interrupts in the safe places
16:55:08
stassats
but the safe place on safepoint makes it exit condition-wait and grab the mutex again
17:00:46
stassats
|3b|: a fix i pushed works here
19:52:45
copec
I wonder if someone could fix this link: http://sbcl-internals.cliki.net/ under http://www.sbcl.org/manual/#Internals-Documentation
19:54:53
copec
well, google -> http://www.sbcl.org/sbcl-internals/
19:55:05
copec
So I guess the manual needs updated.