Closed m0sth8 closed 9 years ago
Thanks for the report.
That looks a lot more like a run-time error than a spew issue from a quick look at this trace, but I'll dig into this a bit more.
Are you dumping C structs/data by chance? I'm fairly certain this means you got a SIGSEGV signal while running C code.
Unfortunately not, I don't have a C structs/data dump. I've got this exception after a week of work under a loading. Also I didn't have this problem with Go 1.3. Spew dumps very complex structure with map, channels, slices and mutexes. Is it possible that go raised panic because structure was modified in another goroutine?
You are running the most recent version of spew as well, right? (go get -u github.com/davecgh/go-spew/spew
) I haven't had a chance to dig into this any more yet, but I figured I'd ask that first since older versions of spew before commit 128854244a4ac24b718da3d5f79cf5541c81ee56 will definitely panic with the go1.4+
runtime.
I used this commit https://github.com/davecgh/go-spew/commit/3fdaf5cea8d23107b993d363e98992fa529dd713 . So I'll update spew and try again. Thank you!
Alright. I'm pretty that was your issue. I'm going to close this, but please comment if you run into any more issues.
Hi! I used go-spew in long running process and had this error: