[144] in Pthreads mailing list archive
Re: Successes with pthreads and X?
daemon@ATHENA.MIT.EDU (William S. Gribble)
Sat Oct 14 23:17:51 1995
From: "William S. Gribble" <grib@cs.utexas.edu>
Date: Sat, 14 Oct 1995 21:56:47 -0500
To: Anselm.Baird_Smith@inria.fr
Cc: pthreads@MIT.EDU
In-Reply-To: <199510121621.RAA11300@maillol.inria.fr> (Anselm.Baird_Smith@inria.fr)
> I used b). I hacked pthreads so that it maintains the global errno
> variable across context switches. If you are interested in diffs let
> me know (although, the remedy and the diffs are really ugly, and will
> not work in all situations).
Could you send me your patches? As ugly as they may be, I need the
functionality...
I had a thought: would it be possible to add a per-thread switch to
determine if __error() returns the global errno or the thread-local one?
That way you could let one thread do all X work, and call
pthread_use_global_errno() at its startup... or similar. Any
reason why it won't work?
Thanks!
Bill Gribble
