On Wed, Jan 15, 2025 at 8:31 PM John <johnsiil...@gmail.com> wrote:
> 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 > Note that simply removing the references to the above mentioned OTEL package does not guarantee the problem is with that package. The failure could still be due to how you are using the package. Having said that, any public package should validate its inputs and provide a more meaningful failure than a SIGSEGV fault. So even if the proximate cause of the failure is a mistake in your code there is clearly room for improvement in the package you are using. As a retired software support engineer who has spent thousands of hours debugging these types of problems I can't stress how important it is to create a minimal reproducible example as the quickest way to get to the root cause of the problem. A minimal reproducible example will allow others, such as the OTEL package maintainers, to employ tools, such as gdb or lldb, which you may not be comfortable using. -- 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/CABx2%3DD8iV%2BABzCgkJ3LFBx-t-axWD7cmWvc6ULBLVgavyJZWuw%40mail.gmail.com.
