Pledge violation messages are no longer accessible through dmesg since
authoranton <anton@openbsd.org>
Mon, 3 Jun 2024 08:02:22 +0000 (08:02 +0000)
committeranton <anton@openbsd.org>
Mon, 3 Jun 2024 08:02:22 +0000 (08:02 +0000)
commit7a7077c028cf38d6f086fdf15b487a0ad276c621
tree4f256f82896a8c07f98ff244390c34877749dca1
parentad2d1a44bc433c192a9a3526b4215ecc6d4aea61
Pledge violation messages are no longer accessible through dmesg since
the switch to uprintf. Attach a pseudo terminal in pledge regress in order to
observe the syscall number that caused the pledge violation, shrug.
regress/sys/kern/pledge/generic/Makefile
regress/sys/kern/pledge/generic/manager.c
regress/sys/kern/pledge/generic/pty.c [new file with mode: 0644]
regress/sys/kern/pledge/generic/pty.h [new file with mode: 0644]