Neal H Walfield <[EMAIL PROTECTED]> writes: > Multithreaded applications cannot safely use the stubs; they > obviously need real locking.
It would be nice to get better error reporting in this case. Perhaps there could a stub for the thread creation function that displays a message and aborts? Or if that is for some reason difficult to get right, one could add a special function ensure_threads_are_enabled that can be called from the multithreaded mainloop in libtrivfs? The implementation included with the stubs should display a message and abort, while the implementation in the real threads library should do nothing. /Niels _______________________________________________ Help-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/help-hurd
