Thanks.
>> Have you eliminated the possibility of races?
We're trying to extract a smaller case for reproducing (perhaps
impractical, as the frequency of the panic is way low) then apply the race
detector, enabling race check online is not an option now, sadly.
>> Have you built with CGO_ENABLED=0?
Building with CGO_ENABLED=0 succeeded, does that mean the binary's runtime
behavior has nothing to do with CGO, deploying
a CGO_ENABLED=0 binary online is not an option as well, for now (We are
trying, but not sure if we can make it happen).
On Thursday, August 17, 2023 at 2:46:16 PM UTC+8 Dan Kortschak wrote:
> On Wed, 2023-08-16 at 23:43 -0700, metronome wrote:
> > Thanks for commenting, a few supplements.
> >
> > # 1. Version of Go?
> > We observed the issue with both go1.20.5 and go1.18.10 on linux/amd64
> > (centos)
> >
> > # 2. Context?
> > All panics we observed so far are from either
> > strconv.FormatInt -> strconv.formatBits chain, or
> > strconv.FormatUint -> strconv.formatBits chain
> > where the base is always 10.
> >
> > // typical call site, toId is an "*int64".
> > if com_count > 1 {
> > com_string = anchor + "," + strconv.FormatInt(*toId, 10)
> > }
> >
> > # 3. If your program using pure Go (statically linked) or Cgo?
> > Binary was built with CGO_ENABLED=1 and -buildmode=exe.
> > All panic call sites we observed so far are "pure go", that is, no C
> > calling go path.
> >
> > # 4. panic stack trace
> > panic: runtime error: index out of range [18446744073708732603] with
> > length 200
> >
> > goroutine 1 [running]:
> > strconv.formatBits({0x0?, 0x0?, 0x0?}, 0xc09e00b750?, 0x1?, 0x1?,
> > 0x0?)
> > /usr/lib/go-1.20/src/strconv/itoa.go:140 +0x4b9
> > strconv.FormatInt(0x0?, 0xc07393df80?)
> > /usr/lib/go-1.20/src/strconv/itoa.go:29 +0xa5
> > ...
>
>
> Have you eliminated the possibility of races? Have you built with
> CGO_ENABLED=0?
>
>
--
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/bc3cde3e-3ed5-4402-b778-a7bd8d7a22c4n%40googlegroups.com.
