On 07/20/2018 02:55 PM, Ian Lance Taylor wrote:
Thanks. But when binutils.test runs /usr/bin/nm -n, it doesn't see
anything? I'm actually not quite clear on what the problem is. Ian
There is a failure when running all.bash as follows:
ok cmd/trace 0.028s
--- FAIL: TestObjFile (0.17s)
binutils_test.go:237: SourceLine for main: expect [{main
/tmp/hello.c 3}]; got [{main 0}]
FAIL
FAIL cmd/vendor/github.com/google/pprof/internal/binutils 0.371s
A similar failure occurs when running the binutils test alone as follows:
go tool dist test -run cmd/vendor/github.com/google/pprof/internal/binutils
It appears that the process running binutils.test forks a process which
calls /usr/bin/nm. This latter process appears to complete correctly
(zero status), and the output of nm can be seen in the strace log. The
process running "binutils.test" appears to fail shortly after the
"/usr/binutils.test" returns.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
