On Wed, Jun 8, 2022 at 4:21 PM Michael Sweeney <starbuck...@gmail.com> wrote:
>
> Hi All, I searched around for details and references for a similar error and 
> could not find anything. I am posting here to see if someone has any pointers 
> to help me discover the root cause.
>
> A GO 1.15.4 executable encountered a panic and generated a core file. Using 
> 'dlv' to analyze the core file, I found:
>
> (dlv) bt
> 0  0x000000000047ee01 in internal/poll.runtime_pollOpen
>    at runtime/netpoll.go:144
> (dlv) frame 0
> > internal/poll.runtime_pollOpen() runtime/netpoll.go:144 (PC: 0x47ee01)
> Warning: debugging optimized function
> Frame 0: runtime/netpoll.go:144 (PC: 47ee01)
> (dlv) args
> fd = 0
> ~r1 = (unreadable empty OP stack)
> ~r2 = (unreadable empty OP stack)
>
> The source code for the above is here:
>
> https://github.com/golang/go/blob/go1.15.4/src/runtime/netpoll.go#L144
>
> I have used the 'latest' and 1.6.0 of 'delve' both report the same details.
>
> Not much else existed. Any suggestions on how one could go about trying to 
> gain more insight into root cause? I have only encountered this once so far.

Normally a panic should print a stack backtrace.  Also the line number
doesn't make sense for a crash.  If this problem has only happened
once, my first guess would be some sort of hardware or kernel failure.
I personally wouldn't spend more time on this kind of failure unless
it happens again.

Note that 1.15.4 is no longer supported.

Ian

-- 
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/CAOyqgcXPVNp6wchF%3Dh%3Dc0FxeuQDakWue2kxvPr2gas0T8OJdNQ%40mail.gmail.com.

Reply via email to