From owner-freebsd-bugs  Mon Jul 12 12:40: 5 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
	by hub.freebsd.org (Postfix) with ESMTP id AF6A11507E
	for <freebsd-bugs@FreeBSD.ORG>; Mon, 12 Jul 1999 12:40:00 -0700 (PDT)
	(envelope-from jin@george.lbl.gov)
Received: (from jin@localhost)
	by george.lbl.gov (8.9.3/8.9.2) id MAA10243;
	Mon, 12 Jul 1999 12:39:54 -0700 (PDT)
Date: Mon, 12 Jul 1999 12:39:54 -0700 (PDT)
Message-Id: <199907121939.MAA10243@george.lbl.gov>
From: jin@george.lbl.gov
To: nate@mt.sri.com
Subject: Re: kern/11984: pthread_kill cannot kill select() threads, etc.
Cc: freebsd-bugs@FreeBSD.ORG, j_guojun@lbl.gov
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Nate,

I just checked out the 3.2-SNAP-19990708, and the problem still remaining.
What would you like to do?

	-Jin

} > } 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