Re: [go-nuts] recover from a unexpected fault address

r > idea of the cause of the problem. > > > > -Original Message- > From: Mayank Jha > Sent: Jul 1, 2019 11:03 AM > To: golang-nuts > Subject: [go-nuts] recover from a unexpected fault address > > unexpected fault address 0x0 > fatal error: fault

Re: [go-nuts] recover from a unexpected fault address

: Mayank Jha Sent: Jul 1, 2019 11:03 AM To: golang-nuts Subject: [go-nuts] recover from a unexpected fault address unexpected fault address 0x0 fatal error: fault [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0xd9c026] goroutine 11707890 [running]: runtime.throw(0x13c74b7, 0x5

Re: [go-nuts] recover from a unexpected fault address

it might give a better idea of the cause of the problem.-Original Message- From: Mayank Jha Sent: Jul 1, 2019 11:03 AM To: golang-nuts Subject: [go-nuts] recover from a unexpected fault address unexpected fault address 0x0fatal error: fault[signal SIGSEGV: segmentation violation code

Re: [go-nuts] recover from a unexpected fault address

Your program dereferenced a NULL pointer. This is most likely to be caused by C/C++ code you've linked with your Go code. You'll need to find out what function is at address 0xd9c026. Try doing "ulimit -c unlimited" to enable a core dump that you can then examine using a debugger like gdb. On

[go-nuts] recover from a unexpected fault address

unexpected fault address 0x0 fatal error: fault [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0xd9c026] goroutine 11707890 [running]: runtime.throw(0x13c74b7, 0x5) /usr/local/go/src/runtime/panic.go:617 +0x72 fp=0xc0080ac5f0 sp=0xc0080ac5c0 pc=0x42f5c2 runtime.sigpanic()