- priority: 5 --> 2
- status: open --> closed-fixed
OriginalBugID: 4826 Bug
Version: 8.3
SubmitDate: '2000-04-03'
LastModified: '2000-07-25'
Severity: SER
Status: Released
Submitter: techsupp
ChangedBy: davidg
RelatedBugIDs: 3862 3423 5791
OS: All Unix
FixedDate: '2000-07-25'
FixedInVersion: 8.4a1
ClosedDate: '2000-07-25'
Name:
David Gravereaux
CVS:
RCS: @(#) $Id: tclUnixPort.h,v 1.13 2000/01/24 02:30:17 hobbs Exp $
Comments:
see bug ID# 3862,3951,3952,3423
Ok, I've posted this bug before, but I just felt like doing
it again. When the thread extension makes it into the core
distribution, these problems will need to be addressed.
BTW, is TclFinalizeCondition and TclpThreadCreate approved
for inclusion in generic/tcl.decls so the thread extension
can be built?
ReproducibleScript:
Create an asyncronous multithreaded extension that calls
Tcl_AsyncMark.
ObservedBehavior:
Notice that when the notifier is asleep on select in
Tcl_WaitForEvent, a call to Tcl_AsyncMark from an
outer thread won't awaken it like it should.
DesiredBehavior:
The notifier awakes like under windows. But the windows
implementation can awaken the wrong notifier when the core
is compiled for thread support.
Example in 3862.
-- 04/04/2000 hobbs
#5791 integrated
-- 07/25/2000 davidg