|
From: Eyal L. <ey...@ey...> - 2007-11-12 11:50:45
|
Sorry to say but this actually did not fix the problem. My first test ran past where it failed before but it did fail later and I can now see that the problem is not resolved. Though the message is slightly different now (tset/lset): Helgrind: Fatal internal error -- cannot continue. Helgrind: mk_SHVAL_ShR(tset=16384,lset=1): FAILED Helgrind: max allowed tset=16383, lset=65535 Helgrind: program has too many thread sets or lock sets to track. Julian Seward wrote: >> Helgrind: Fatal internal error -- cannot continue. >> Helgrind: mk_SHVAL_ShR(tset=8192,lset=1): FAILED >> Helgrind: max allowed tset=8191, lset=131071 >> Helgrind: program has too many thread sets or lock sets to track. > > Yes. It's a problem I'm tracking. Really it is trying to squeeze > too much information into a 32-bit word. It's probably fixable properly > at some performance loss. > > In the meantime, at hg_main.c:902 reduce N_LSID_BITS from 17 to 16 and > try again. > > J -- Eyal Lebedinsky (ey...@ey...) |