Nathan J. Williams writes:
> > ... [quoted thread removed]
> 
> This is getting a bit out of control.
> 
> Can someone name an example of a genuinely threaded, as opposed to
> defensively-mutex-using, loadable module for some app?

The commercial application I referred to earlier is a non-threaded
Verilog circuit simulator which provides demand loading for user
and third-party code using the PLI/VPI API. Such code is increasingly
being written using threads (actually creating threads, not just
defensive coding).

The failure modes across various OS platforms make the support
issues "interesting".  The anecdote regarding Solaris sigaction
side-effects comes from a real-world failure report. Adding thread
libraries into the application link step would resolve that problem
at the cost of significant performance.

Sorry, its not an example where the source, for either the app or
the loaded module, is available for inspection.  But it is at least
a real-world occurence.

/sjd