If we got interrupted while waiting on our condition variable, we unlock
the kernel mutex momentarily while executing asynchronous operations
before putting us back into the waiting queue.
However, we have to retry acquiring the mutex before getting back into
the queue, otherwise it's possible tha
work on
Guile core itself, myself included. However, I find it difficult to
contribute in general and to have feedback.
--
Olivier Dion
oldiob.dev
hen there is callbacks .. and other things ..
The above link gives comments on all of this but not much details.
Hope that helps.
--
Olivier Dion
oldiob.dev
their desk. e.g., (srfi srfi-1) => (srfi list) or
something like that.
[...]
--
Olivier Dion
oldiob.ca
ile 4 is out, I
think ice-9 should be kept to ease transition from 3 to 4. At the same
time, major version bumping also mean API breakage .. so it might be a
good opportunity.
However, if a (guile ...) hierarchy is introduced, all mentions to
ice-9, except the historical note, ought to be removed from the manual.
[...]
--
Olivier Dion
oldiob.ca
hi - lo; lo + lenght < lo => Unsigned integer overflow
3) The memory range is locked. See mlock(2)
4) The variable `page_size' is zero for some reason (highly doubt)
You can check for all of the above with a debugger or `strace(1)'
easily.
Regards,
Olivier
--
Olivier Dion
oldiob.ca
