[M3devel] "port simple race condition fix from head related to stopping a thread before/after it has any traced references"

Tony Hosking hosking at cs.purdue.edu
Fri Dec 11 15:57:13 CET 2009


On 11 Dec 2009, at 06:22, Jay K wrote:

> Something is fishy here. The change is fine, but there could only be a problem
> if suspending the thread didn't work? You know, the stack value shouldn't
> be changing? I'm pretty sure I saw this be a problem on some configuration,
> but maybe it was only user threads and maybe they are relevantly different?
>  
> Also Tony is it ok to RTHeapRep.FlushThreadState unconditionally here?

I think so: only stopped threads have this done to them.  If they are using the thread state (for allocation) then they are inCritical.

>  
>  - Jay
>  
> > Date: Fri, 11 Dec 2009 12:14:26 +0000
> > To: m3commit at elegosoft.com
> > From: jkrell at elego.de
> > Subject: [M3commit] CVS Update: cm3
> > 
> > CVSROOT: /usr/cvs
> > Changes by: jkrell at birch. 09/12/11 12:14:26
> > 
> > Modified files:
> > cm3/m3-libs/m3core/src/thread/PTHREAD/: Tag: 
> > release_branch_cm3_5_8 
> > ThreadPThreadC.c 
> > 
> > Log message:
> > port simple race condition fix from head related to stopping a thread before/after it has any traced references
> > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20091211/483b5e8e/attachment-0002.html>


More information about the M3devel mailing list