Thank you for raising this issue. Would you please supply a runnable code sample that shows the problem. Thank you

@davecheney
case code

package main

import (
	"context"
	"fmt"
)

func main() {
	ctx := context.WithValue(nil, "test-key", "test-val")
	val := ctx.Value("not-exist-key")

	fmt.Println(val)
}

result

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

goroutine 1 [running]:
context.(*valueCtx).Value(0xc00006a180, 0x10ac320, 0x10e9f50, 0x10e9f30, 0x10ac320)
        /usr/local/go/src/context/context.go:553 +0x3f
main.main()
        /Users/wangjunchao/go/src/wangjunchao/value_context_panic/value_context_panic.go:10 +0x82

Please don’t pass nil as the parent context. This is documented in the package preamble.

Do not pass a nil Context, even if a function permits it. Pass context.TODO if you are unsure about which Context to use.

https://godoc.org/context

The Go project doesn't use the issue tracker for questions. See https://golang.org/wiki/Questions.

It seems like Dave clarified your problem above, so I'm closing this for now. In the future, please try one of the forums for questions.

Is the line

return c.Context.Value(key)

Concurrent Safe?

The stack trace of error I am receiving is attached

This panic is arising when a lot of read is happening to context value.

Please don't comment on old issues that were closed as questions. See the wiki link I shared.