Thanks, Ian.
On Fri, 2016-10-07 at 07:05 -0700, Ian Lance Taylor wrote:
>
> 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
On Thu, Oct 6, 2016 at 10:38 PM, Dan Kortschak
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 b
On Fri, 2016-10-07 at 06:00 +, 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
On Fri, Oct 7, 2016 at 7:39 AM Dan Kortschak
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?
Perhaps the pani
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 addres
