Date: Mon, 05 May 2003 21:44:25 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Daniel Eischen <eischen@pcnet1.pcnet.com>, David Xu <davidxu@viatech.com.cn>, threads@freebsd.org Subject: Re: Patch for running Java2D demo (jdk-1.4.1p3_3) Message-ID: <3EB73DA9.B0F0C647@mindspring.com> References: <Pine.GSO.4.10.10305050710430.15251-100000@pcnet1.pcnet.com> <3EB7256E.844A5958@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Daniel Eischen wrote: > > > Personally, I don't think this is justifiable, and that the > > > problem is actually a coding error in the threaded program, > > > with failure to comply with the POSIX and Single UNIX > > > Specification when writing your threaded program. The pthreads > > > documentation seems to back me up (Chapter 12 of "Go Solo 2", > > > as well as Corrigenda). > > > > It *is* an rtld-elf problem. I've protected dlfoo() all with the > > same mutex and it still hangs. rtld-elf uses spinlocks in > > areas that aren't called by dlfoo(). Rather than pointing at the standards over and over again, it occurs to me that I should ask you a question, instead, to emphasize our disconnect; so here it is: If my theory of operation for the bug was incorrect, can you tell me *why* my suggested scheduler workaround fixed it, instead of having no effect or only a partial effect? Thanks, -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EB73DA9.B0F0C647>