OK, so you're not using Cgo, that leaves some other unsafe use, a data race or unlikely some weird compiler bug.
I'd start looking in api.handleDPriceRange to see where the string input to strconv.ParseFloat is being constructed. On Fri, 2020-11-06 at 01:10 -0800, blade...@gmail.com wrote: > go version is 1.15 , cross compile on darwin and run on linux, i > will try to run with race deector > > > > 在2020年11月6日星期五 UTC+8 下午4:34:21<kortschak> 写道： > > The full panic would help, but somehow you have a string with a > > nil > > pointer that is 4 bytes long. Where is the string generated? Are > > you > > using Cgo? Have you run with the race detector? Also, what version > > of > > Go are you using? > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/dc04cd21bb00f2e520f9791fdad6c1731c85a8a2.camel%40kortschak.io.
