I am trying to use helgrind and so far I have a showstopper. Simplified, my software is a number of servers and clients. The clients execute a heartbeat connection to one server (1/sec).
Bringing up the servers and clients all looks fine but very soon (90s after it actually starts running) one server exits. Another exits a few minutes later, then the last one survives for much longer. The vg logs always end with this report: 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. ... My servers were effectively idle at this point, the real work did not even start. There were only a dozen threads "created" by any server by the time it fails. The program uses pthreads, nothing fancy, the testing is done on Linux Debian 3.1 on x86, libc-2.3.2. Latest vg off svn. -- 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 Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
