|
From: Christian P. <tr...@ge...> - 2005-08-08 07:03:42
|
Hi, I am just about to use helgrind (my first time) on my app to track down som= e=20 mutex/synchronization issues (I hope this is the right tool to do so ;). however, when starting VG/helgrind, it (waits the usual freezing time, and= =20 then) just exits without any further notice. Well, a little modifying the commandline and re-invoking the command finally results into a SEGFAULT of (obviousely) helgrind. Is this a known (mis-)behavior? Regards, Christian Parpart. =2D-=20 08:59:49 up 137 days, 22:07, 0 users, load average: 1.02, 2.18, 2.27 |