[concurrency-interest] RRWL with 'bad' Thread.getId() implementations

Chris Hegarty chris.hegarty at oracle.com
Tue Jun 25 18:26:40 EDT 2013


On 25 Jun 2013, at 22:20, Martin Buchholz <martinrb at google.com> wrote:

> On Tue, Jun 25, 2013 at 2:16 PM, Aleksey Shipilev <aleksey.shipilev at oracle.com> wrote:
>> On 06/26/2013 01:13 AM, Martin Buchholz wrote:
>> On the serious note, we need to frame this discussion a bit. Do you want
>> the bug against RRWL with the testcase Chris had came up with? (That is,
>> do you agree this is the bug in RRWL?)
> 
> I think I agree this is a small bug in RRWL, but I suspect any attempt to cure it would be worse than the disease.

Even with the addition of Thread.getFinalId() in jdk8? It would seem like RRWL could be "fixed" for free!

-Chris


> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20130625/43b78695/attachment.html>


More information about the Concurrency-interest mailing list