tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49985] Lazy initialization without any synchronization - data race in AstInteger, AstFloatingPoint, AstString
Date Fri, 01 Oct 2010 13:34:50 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49985

--- Comment #8 from Sergey Vorobyev <sergeyvorobyev@google.com> 2010-10-01 09:34:45
EDT ---
(In reply to comment #7)
> (In reply to comment #6)
> > Lock at this stack-traces to see how this method can be on invoked from a
> > number of threads:
> 
> But is each thread in the pair using the same instance?  There's no evidence of
> that in the published trace.

I omit first line of race report, sorry.

WARNING: Possible data race during write of size 1 at 0x76a1569c: {{{
 ...

Where 0x76a1569c is hashCode of object and field.

Also I always add something like this in critical sections:

int hash = System.identityHashCode(this);
long tid = Thread.currentThread().getId();
System.out.println(">>VER>> START WRITE/READ " + tid + " " + hash);
try {
    Thread.sleep(10);
} catch (InterruptedException e) {
throw new RuntimeException(e);
}

System.out.println(">>VER>> END WRITE/READ " + tid + " " + hash);    

And analise stdout. 
This race was verified.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message