Re: [go-nuts] fatal error: bad pointer in write barrier

2016-12-02 Thread 'Florian Uekermann' via golang-nuts
> > You wrote `*X.Y`; I'm going to assume you meant to write `*X = Y`. > *X.Y = value , where the Y field is a pointer to the C heap. But I suppose that is pretty much the same. > This error message is telling you that in the assignment `*X = Y` Y > has a pointer type, but has the value 1.

Re: [go-nuts] fatal error: bad pointer in write barrier

2016-12-01 Thread Ian Lance Taylor
On Thu, Dec 1, 2016 at 4:47 PM, 'Florian Uekermann' via golang-nuts wrote: > > I just had a fairly strange not reproducible panic. I have no idea whether > this could be a go bug or if the C library I am using is buggy. In case it > looks like a go bug I should probably post this on the issue trac

[go-nuts] fatal error: bad pointer in write barrier

2016-12-01 Thread 'Florian Uekermann' via golang-nuts
I just had a fairly strange not reproducible panic. I have no idea whether this could be a go bug or if the C library I am using is buggy. In case it looks like a go bug I should probably post this on the issue tracker. Does anyone have an idea whether this is useful or if I should just forget a