On Thu, Oct 6, 2016 at 10:38 PM, Dan Kortschak <dan.kortsc...@adelaide.edu.au> wrote: > I have just been given the following stack trace for a program I working > on. The trace terminates before it gets into my program, making it's > utility close to zero. Does anyone have any idea why it is not extending > into main? > > $ go build back.go > $ ./back > panic: runtime error: invalid memory address or nil pointer dereference > [signal SIGSEGV: segmentation violation code=0x1 addr=0x68 pc=0x458b26] > > goroutine 5 [running]: > panic(0x4fa640, 0xc42000c0f0) > /home/daniel/Development/go/src/runtime/panic.go:500 +0x1a1 > bytes.(*Buffer).ReadFrom(0x0, 0x59b6c0, 0xc420036048, 0xc420033e88, 0x1, > 0x0) > /home/daniel/Development/go/src/bytes/buffer.go:158 +0x26 > io.copyBuffer(0x59b340, 0x0, 0x59b6c0, 0xc420036048, 0x0, 0x0, 0x0, 0x0, > 0x0, 0x0) > /home/daniel/Development/go/src/io/io.go:384 +0x323 > io.Copy(0x59b340, 0x0, 0x59b6c0, 0xc420036048, 0x0, 0x0, 0x0) > /home/daniel/Development/go/src/io/io.go:360 +0x68 > os/exec.(*Cmd).writerDescriptor.func1(0x0, 0x0) > /home/daniel/Development/go/src/os/exec/exec.go:253 +0x4d > os/exec.(*Cmd).Start.func1(0xc4200806e0, 0xc4200106e0) > /home/daniel/Development/go/src/os/exec/exec.go:370 +0x27 > created by os/exec.(*Cmd).Start > /home/daniel/Development/go/src/os/exec/exec.go:371 +0x4db
This is a case where the default traceback is letting you down, because the failing goroutine was started by the os/exec package. You want to set GOTRACEBACK=all to get more useful data. Ian -- 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.
