On Fri, 2016-10-07 at 06:00 +0000, Jan Mercl wrote: > Perhaps the panic occurs in some init() function and/or a TLD variable > initializer? FTR, the panic is here: > https://github.com/golang/go/blob/f75aafdf56dd90eab75cfeac8cf69358f73ba171/src/bytes/buffer.go#L158 > I've figured out the cause of the panic - I was passing a nil bytes.Buffer when I meant to pass a nil io.Writer, and it happens when and exec.Cmd is Run. But it would be nice if it didn't require a print statement bisection to get to that conclusion.
-- 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.
