|
From: Alexander P. <gl...@go...> - 2011-07-28 20:46:47
|
Running the binaries under Nullgrind (valgrind --tool=none) is better to start with, because Go programs are likely to trigger some incompatibilities in the Valgrind runtime itself, not necessarily Memcheck. For example, goroutines may be tricky to mirror in a straightforward way (using threads), because there can be thousands of them, while Valgrind has a strict limit for the number of threads. Second, they use segmented stacks in Go, which are extended if needed. Valgrind does not know about this and may be confused (I suppose the segfaults in your report could denote the demand for increasing the stack size) A side question: is there any particular reason you need Valgrind for Go? Alex |