both on 32bit Linux VMS, while 64bit VMs seem to work fine. This was
on Go 1.2.1, and I asked whether it still happens on tip:
runtime: newstack called from g=0x93be5140
m=0x93bf3000 m->curg=0x0 m->g0=0x93be51e0 m->gsignal=0x93be5140
fatal error: runtime: wrong goroutine in newstack
From the full traceback , this is happening during a call where Go
calls C calls Go, right at the entrance back into Go.
Would anyone have a clue, before I try to setup an environment to dig
further into it?
gustavo @ http://niemeyer.net
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/d/optout.