On 12/17/2013 10:05 AM, Jafar Al-Gharaibeh wrote: ... > I commented out the lines that depends on the package and I was able to move > on and reproduce your problem. > > We have recently made changes to the runtime/VM so that in sequential > programs they ignore (for the most part) any > concurrency related code, this is mainly done to avoid reduce overhead for > programs that don't use concurrent threads. > When concurrency is detected, the concurrency code kicks-in. In your code, a > call to mutex() (which triggers concurrency > features) happens in the middle of an initial clause (which itself is a > critical region) causing the critical region to > try to unlock, even though it started unlocked! > > Nice catch! The problem is fixed an committed to svn. Please update and let > me know if you have any other issues.
Thanks - works great again! -- Steve Wampler -- swamp...@noao.edu The gods that smiled on your birth are now laughing out loud. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Unicon-group mailing list Unicon-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unicon-group
