|
From: Albert S. <fu...@gm...> - 2011-07-28 21:51:16
|
Hello On Thu, Jul 28, 2011 at 11:46 PM, Philippe Waroquiers <phi...@sk...> wrote: > On Thu, 2011-07-28 at 23:33 +0200, Albert Strasheim wrote: >> Warning: Unfortunately, this client request is unreliable and best avoided. >> Is this still the case with Valgrind in SVN? >> If so, is this something that could be fixed relatively easily or are >> there dragons here? > The svn doc still contains the same warning. > But the doc also tells: > "Use this if you're using a user-level thread package and are noticing > spurious errors from Valgrind about uninitialized memory reads." I'm seeing what I think are spurious errors for the Go binaries that do run to completion under Valgrind. I don't think this will fix the SIGSEGV, > I am not sure an valgrind SEGV matches this. > Do you see the same crash with other tools ? > (e.g. callgrind/cachegrind/massif/...) ? Agreed. The segfault is a separate problem that has to be addressed. Regards Albert |