Date: Fri, 9 Jul 1999 09:57:02 -0600 From: Nate Williams <nate@mt.sri.com> To: jin@george.lbl.gov Cc: j_guojun@lbl.gov, nate@mt.sri.com, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/11984: pthread_kill cannot kill select() threads, etc. Message-ID: <199907091557.JAA06226@mt.sri.com> In-Reply-To: <199907091542.IAA04652@george.lbl.gov> References: <199907091542.IAA04652@george.lbl.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
> } Note, according the PR, you are running: > } > } >Release: FreeBSD 3.2-RELEASE i386 > } > } > > } > By tracing downto c_r library, two problems have been found: > } > > } > (1) pthread_exit(void *status) ... > } Which version of FreeBSD are you using? In 3.0, it was a char, so I'll > } bet you are using a buggy version of the library. Please update to a > } more recent version, which has these bugs fixed. > > Sorry for the confusion. That was in 2.2.8-RELEASE. The problem is the > gdb get core dump under 3.2-RELEASE when attach the hanging process, > so I did debugging under 2.2.8-RELEASE. The GDB bug was fixed in 3.2-stable right after the release, so please upgrade to 3.2-stable. > Yes, part of the problem 1 is fixed in 3.2-RELEASE, but the flags is not > checked any where, which causes problem 2 still in 3.2. Can you check out the stock code, and if it's still a problem followup on this PR? > If you agree this logic, I will examine the code and add this conditional > code to fix the problem. Let's wait until after you upgrade, and see if the problem still exists. It's possible it may have been fixed some other way. Thanks! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907091557.JAA06226>