runtime: openbsd fork-exec calls exit instead of _exit in failed child

Open rsc opened this issue 3 years ago • 5 comments

As part of work on CL 459176 I noticed that the libc ports are calling exit(3) instead of _exit(2). I fixed Darwin in that CL but did not want to touch OpenBSD so close to the release if it wasn't obviously broken. Probably a bad atexit handler could foul up the fork child, and _exit should be used instead. Needs investigation and probably a fix.

Dec 22 '22 15:12 rsc

CC @golang/openbsd.

Dec 22 '22 16:12 dmitshur

Change https://go.dev/cl/459176 mentions this issue: runtime: call __fork instead of fork on darwin

Dec 22 '22 18:12 gopherbot

Change https://go.dev/cl/459178 mentions this issue: runtime: call __fork instead of fork on darwin

Dec 22 '22 18:12 gopherbot

Change https://go.dev/cl/459178 mentions this issue: [release-branch.go1.19] runtime: call __fork instead of fork on darwin

Dec 22 '22 18:12 gopherbot

Change https://go.dev/cl/459179 mentions this issue: [release-branch.go1.18] runtime: call __fork instead of fork on darwin

Dec 22 '22 18:12 gopherbot