Hi,
Thanks for looking into it!
However, I see two issues:
1. We can’t really change ‘scm_with_guile’, because it’s a public
function, and it’s been there “forever”.
2. Fundamentally, there should be no limit other than that imposed by
the OS (or hardware resources) on the number of threads.
Doug Evans (hi! :-)) was looking at signal-handling code, suggesting he
may come up with another implementation of signal-handling that does not
involve the current signal delivery machinery.
That machinery happens to also be the root of the problem at hand,
because it mandates this pipe between newly-created threads and the
signal-delivery thread.
So I think this is really the way to go.
Ludo’.
