os/exec: panic in (*Cmd).Start.func2 on openbsd-amd64-68

[bcmills]

https://storage.googleapis.com/go-build-log/84130882/openbsd-amd64-68_97af332c.log (a TryBot):

            > go test -v foo_test.go
            [stderr]
            panic: runtime error: invalid memory address or nil pointer dereference
            [signal SIGSEGV: segmentation violation code=0x1 addr=0x1 pc=0x55f005]
            
            goroutine 441 [running]:
            panic({0xa57620, 0xf64e30})
            	/tmp/workdir/go/src/runtime/panic.go:969 +0x3ba fp=0xc00073a778 sp=0xc00073a6b8 pc=0x437bda
            runtime.panicmem(...)
            	/tmp/workdir/go/src/runtime/panic.go:242
            runtime.sigpanic()
            	/tmp/workdir/go/src/runtime/signal_unix.go:823 +0x336 fp=0xc00073a7c8 sp=0xc00073a778 pc=0x44e396
            os/exec.(*Cmd).Start.func2()
            	/tmp/workdir/go/src/os/exec/exec.go:537 +0x25 fp=0xc00073a7e0 sp=0xc00073a7c8 pc=0x55f005
            runtime.goexit()
            	/tmp/workdir/go/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc00073a7e8 sp=0xc00073a7e0 pc=0x46bba1
            created by os/exec.(*Cmd).Start
            	/tmp/workdir/go/src/os/exec/exec.go:535 +0x6be

[bcmills]

Marking as release-blocker until I can determine whether this is related to CL 401896.

[bcmills]

greplogs -l -e \\s+os/exec\\.\\\(\\\*Cmd\\\)\\.Start\\.func2\\\(\\\)
2022-05-08T17:26:10-df57592/plan9-amd64-0intro
2021-12-13T16:44:13-27fc764-acc65b4/netbsd-amd64-9_0-n2d

(But neither of those matches this failure mode.)

[bcmills]

greplogs -l -e '(?ms)panic: runtime error: invalid memory address.*^os/exec\.\(\*Cmd\)\.Start' --since=2022-05-08

(0 matching logs)

Looks to me like this was some kind of memory corruption (CC @golang/openbsd).

AFAICT it is not a systematic problem with the os/exec change.

[bcmills]

Duplicate of #34988