Comment 1:

Does termite use cgo?

Comment 2:

No.

Comment 3:

termite does use plenty of unsafe, iirc.  Does the GC promise not to crash in the
presence of memory shenanigans?

Comment 4:

go-fuse uses unsafe.  It might be linked in shell-wrapper (which is the 'interceptor'),
but not run in there. moreover, no termite/go-fuse has been run at this point, as the
code is running init() for strings and unicode packages.

Comment 5:

Labels changed: added priority-later, removed priority-medium.

Comment 6:

Labels changed: added priority-go1.

Comment 7:

Status changed to Accepted.

Comment 8:

Owner changed to builder@golang.org.

Comment 9:

Running a fmt-based hello world in a loop was enough to trigger this panic, about one
run per million, when I was testing back in October.  Would be nice to track down, but
likely not before Go 1.

Labels changed: added priority-later, removed priority-go1.

Comment 10:

Labels changed: added go1.1maybe.

Comment 11 by sebastien.paolacci:

Is someone still able to (even remotely) reproduce that kind of "basic" crash?
Last fix I can remember in that area was Dmitriy's one (last October), but the guilty
piece of code was not present in weekly.2011-10-18.
At glance, it looks like that issue relevance has just vanished over the time (and
general code improvement). If someone can inject some more info, I may however try to
chase it down.
Thanks,
Sebastien

Comment 12:

Let's assume this is fixed, and if not assume we'll get a better report.

Status changed to Unfortunate.

Comment 13 by sebastien.paolacci:

Ok, thanks.