I think this isn't exactly the problem you're looking for. You get > "waitpid: No child pocesses" because Racket (with places enabled) > creates its own thread to reap child processes. >
Is it possible to make Racket not to reap child processes? Can it be done during its initialization or is compilation without places the only option? > But if you're embedding Racket with other libraries, then the problem > may boil down to the same issue: Racket maybe isn't playing nicely > enough with the other libraries, which might create their own threads > that have SIGCHLD enabled. > > If I remember correctly, Racket blocks SIGCHLD in the main thread when > it starts up, so that all new threads that Racket creates inherit this > disposition. In your emebdding application, do other libraries maybe > create threads before Racket is initialized, so that they could be > created with SIGCHLD unblocked? > > I see, we have two different problems here. One is reaping child processes and another is unblocked SIGCHLD. Thanks.
____________________ Racket Users list: http://lists.racket-lang.org/users
