Julian,
Thanks, this fixes it.
Can I ask a question then?
I notice that I am getting race reports for situations where I
am rather sure that the only active thread is the main thread.
My programs do not apply locks in these sections of the code,
for example during server shutdown after all threads were
join'ed.
Is this possible or should I check my program again?
cheers
Eyal
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 ([EMAIL PROTECTED])
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
