Re: thread::mutex lock problem, a bug?
- From: "Abuda" <haoning_fu@xxxxxxxxx>
- Date: 3 Feb 2006 06:32:58 -0800
I found what was wrong:
When I compiled thread extension, I put it at the same directory of
tcl8.4.11 which is compiled without --enable-threads.
After I recompiled it, every thing is fine. I removed all "after"
statement, and run it for one hour. No deadlock or starvation is
observed.
I am going to test my real applications. some of them are running under
MS windows. Do you have to update windows code? How soon will
activestate.com update your modifications?
I will tell you the testing result soon.
Thank you.
.
- Follow-Ups:
- Re: thread::mutex lock problem, a bug?
- From: Zoran Vasiljevic
- Re: thread::mutex lock problem, a bug?
- References:
- Re: thread::mutex lock problem, a bug?
- From: Abuda
- Re: thread::mutex lock problem, a bug?
- From: Zoran Vasiljevic
- Re: thread::mutex lock problem, a bug?
- From: Abuda
- Re: thread::mutex lock problem, a bug?
- From: Zoran Vasiljevic
- Re: thread::mutex lock problem, a bug?
- Prev by Date: Re: Getting a file from http
- Next by Date: Re: Segmentation fault in internal Tcl function
- Previous by thread: Re: thread::mutex lock problem, a bug?
- Next by thread: Re: thread::mutex lock problem, a bug?
- Index(es):