Date: Thu, 05 Jun 2003 04:41:31 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Daniel Eischen <eischen@pcnet.com> Cc: freebsd-threads@freebsd.org Subject: Re: FreeBSD pthread_equal "bug" Message-ID: <3EDF2C6B.7A8E5C21@mindspring.com> References: <Pine.GSO.4.10.10306041126030.13583-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Eischen wrote: > Process id's can wrap around so it can eventually happen. > > This is a bug in the application; the implementation is allowed > to reuse thread id's and there are enough interfaces for an > application to tell when a thread terminates (pthread_join). > > Perhaps our use of thread id's could be changes so that they > were cached at the end of the free thread list, but cacheing > them at the front seems to highlight bad applications, so > that's a bonus ;-) So's not explicitly protecting dlopen(), and so's not forcing rescheduling of the thread that was running at preemption time, when returning from an involuntary preemption. ;^). If you're willing to hack around these two, why not the thread ID as well? 8-) 8-). -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EDF2C6B.7A8E5C21>