Getting nil pointer references when log.SetHandler(...) is not set

Question

Getting nil pointer references when log.SetHandler(...) is not set

matthewmueller opened this issue 8 years ago · comments

Is there anyway to prevent this? I'd love to use this library more like debug (logging within nested packages), seems like the default should be discard.

Definitely down to open a PR with a bit of direction :-)

Looks like this:

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x1d053c]

goroutine 5 [running]:
panic(0x283620, 0xc42000c0d0)
	/usr/local/Cellar/go/1.7.4_1/libexec/src/runtime/panic.go:500 +0x1a1
testing.tRunner.func1(0xc420094180)
	/usr/local/Cellar/go/1.7.4_1/libexec/src/testing/testing.go:579 +0x25d
panic(0x283620, 0xc42000c0d0)
	/usr/local/Cellar/go/1.7.4_1/libexec/src/runtime/panic.go:458 +0x243
github.com/apex/log.(*Logger).log(0xc420010200, 0x1, 0xc420105988, 0xc420018be0, 0x9e)
	/Users/matt/go/src/github.com/apex/log/logger.go:125 +0x6c
github.com/apex/log.(*Entry).Info(0xc420105988, 0xc420018be0, 0x9e)
	/Users/matt/go/src/github.com/apex/log/entry.go:61 +0x50
github.com/apex/log.(*Logger).Info(0xc420010200, 0xc420018be0, 0x9e)
	/Users/matt/go/src/github.com/apex/log/logger.go:68 +0x7f
github.com/apex/log.Info(0xc420018be0, 0x9e)
	/Users/matt/go/src/github.com/apex/log/pkg.go:44 +0x49

TJ Holowaychuk · Answer 1 · Sun Jan 15 2017 00:17:54 GMT+0800 (China Standard Time)

hmm you miiiight have to go get -u github.com/apex/log to grab the recent stuff, it should have a default stdlib log handler by default

Matt Mueller · Answer 2 · Sun Jan 15 2017 17:05:03 GMT+0800 (China Standard Time)

:-O Let me try that!

…

On Sat, Jan 14, 2017 at 11:17 PM TJ Holowaychuk ***@***.***> wrote: hmm you miiiight have to go get -u github.com/apex/log to grab the recent stuff, it should have a default stdlib log handler by default — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKZO_33xiirDPqEok9bjFWaijTPRSXlks5rSPUygaJpZM4Ljl3o> .

Matt Mueller · Answer 3 · Mon Jan 16 2017 15:27:19 GMT+0800 (China Standard Time)

yep, that did the trick – sorry for the false alarm!