Hey Kurtis, Thanks for responding.
Unfortunately, this does look like some type of OTEL problem. I was able to make a copy and strip out all the OTEL code. As soon as I did this, this stopped happening. Which means it is some type of OTEL issue that I should probably track down with the OTEL people. As a note for someone who stumbles on this with a similar problem, the OTEL packages included: "go.opentelemetry.io/otel/attribute" "go.opentelemetry.io/otel/trace" "go.opentelemetry.io/otel/metric" These packages are at v1.33.0 If and when I track down the cause, I'll post an update here. Thanks again Kurtis! On Wednesday, January 15, 2025 at 7:53:40 PM UTC-8 Kurtis Rader wrote: > That your failure backtrace only has Go garbage collection threads and > your main thread is slightly surprising. It does look like your main > function is calling C code that is causing the SIGSEGV. Can you show us > your "main" package? You say you're using "various OTEL packages". Which > ones specifically? I'm guessing you're using > https://github.com/open-telemetry/opentelemetry-go but we shouldn't have > to guess. I haven't used that package but it would not surprise me if it > created OS threads that run C code. In this type of situation the most > likely cause is a mistake in your code. Second most likely is a bug in a > third-party package you're using. A distant third is a bug in the Go > runtime, the OS, etc. > > You also wrote "I've attempted to build a binary out of it and run it, > with the same results." But it's unclear what you did. I interpret that > sentence to mean you did "go build" and ran the resulting binary rather > than running unit tests via "go test". Can you clarify what you mean by > "build a binary out of it and run it"? > > On Wed, Jan 15, 2025 at 6:49 PM John <johns...@gmail.com> wrote: > >> I'm running into a fault now when trying to run `go test -race`/ >> >> I get the same when I disable CGO (because it lists a CGO signal in the >> fault): >> `CGO_ENABLED=0 go test -c -race` >> >> I've attempted to build a binary out of it and run it, with the same >> results. This is not happening on all tests I attempt, just some tests. >> >> I don' know of any C code I'm using, but I am importing various OTEL >> packages, which might have CGO somewhere. >> >> I'm not sure where to start debugging this, the internet has pointed to >> other issues similar to this, not exact and none with circumstances that >> are the same. >> >> Here is the fault: >> >> SIGSEGV: segmentation violation >> PC=0x10012c23c m=0 sigcode=2 addr=0x10 >> signal arrived during cgo execution >> > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank > -- 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 visit https://groups.google.com/d/msgid/golang-nuts/e43954c1-f9c1-4a71-9f60-f028cbdfb906n%40googlegroups.com.