Re: [rvm-research] Bug: Locks returned from thread cachedFreeLock are not marked active
David P Grove <[email protected]>
| Newsgroups | gmane.comp.java.jikes.rvm.devel |
|---|---|
| Message-ID | <OF86D9701E.7B4F6D4D-ON85257B5A.00105959-85257B5A.00106673@us.ibm.com> |
Carl Ritson <[email protected]> wrote on 04/23/2013 01:15:06 PM: > > I noticed that in the code path for Lock.allocate() which returns a > cached lock from RVMThread's cachedFreeLock the lock returned is not > marked active. The only impact of this as far as I can tell is that > many locks will not be reported via dumpLocks(), for example when the > VM fails. This can hamper debugging, but that's all. > > Attached is a one line diff to fix this bug. > Thanks Carl. Bug fixed in tip. --dave ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Jikesrvm-researchers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers