freenode/#sbcl - IRC Chatlog
Search
18:40:45
stassats
the CI is telling that run-program can still not only deadlock but also produce SIGILL
18:55:31
stassats
unrelated to the deadlocks, maybe posix_spawn can be applicable to sb-ext:run-program
21:20:19
stassats
so much advice on the internet is wrong, like all the people trying to convince that fork+exec is really fast because of CoW
21:22:42
stassats
maybe interrupting fork is not a good idea and i should push the change that moves forking into a separate non-lisp thread
21:31:07
stassats
i actually want two dedicated threads for run-program houskeeping, the C one will fork, handle SIGCHLD and the lisp one will handle input/output polling
21:40:51
stassats
a dedicated thread doesn't help, seems like malloc itself is broken, maybe there's just no progress, not a real lock