[Bug 261018] An online manual page for FreeBSD 13.0-RELEASE misrepresents features that are in stable/13 – not released

On 07/01/2022 23:33, Graham Perrin wrote: Before I open a website bug report, someone please check my interpretation: * <621b5090487de9fed1b503769702a9a2a27cc7bb> (Refactor configuration management in bhyve) was committed 2021-03-18, MFC after three months, however (for whatever reason, not m

bhyve(8) manual page misrepresentation, option -k in particular

Before I open a website bug report, someone please check my interpretation: * <621b5090487de9fed1b503769702a9a2a27cc7bb> (Refactor configuration management in bhyve) was committed 2021-03-18, MFC after three months, however (for whatever reason, not my concern) it is _not_ yet in stable/13 *

Re: FYI: An example type of UBSAN failure during kyua test -k /usr/tests/Kyuafile

On 2022-Jan-7, at 04:31, Stefan Esser wrote: > Am 07.01.22 um 12:49 schrieb Mark Millard: >> Having done a buildworld with both WITH_ASAN= and WITH_UBSAN= >> after finding what to control to allow the build, I installed >> it in a directory tree for chroot use and have >> "kyua test -k /usr/te

Re: FYI: An example type of UBSAN failure during kyua test -k /usr/tests/Kyuafile

On 2022-Jan-7, at 05:08, Mark Millard wrote: > On 2022-Jan-7, at 03:49, Mark Millard wrote: > >> Having done a buildworld with both WITH_ASAN= and WITH_UBSAN= >> after finding what to control to allow the build, I installed >> it in a directory tree for chroot use and have >> "kyua test -k /usr

Re: FYI: An example type of UBSAN failure during kyua test -k /usr/tests/Kyuafile

On 2022-Jan-7, at 03:49, Mark Millard wrote: > Having done a buildworld with both WITH_ASAN= and WITH_UBSAN= > after finding what to control to allow the build, I installed > it in a directory tree for chroot use and have > "kyua test -k /usr/tests/Kyuafile" running. > > I see evidence of variou

Re: FYI: An example type of UBSAN failure during kyua test -k /usr/tests/Kyuafile

Am 07.01.22 um 12:49 schrieb Mark Millard: > Having done a buildworld with both WITH_ASAN= and WITH_UBSAN= > after finding what to control to allow the build, I installed > it in a directory tree for chroot use and have > "kyua test -k /usr/tests/Kyuafile" running. > > I see evidence of various ex

FYI: An example type of UBSAN failure during kyua test -k /usr/tests/Kyuafile

Having done a buildworld with both WITH_ASAN= and WITH_UBSAN= after finding what to control to allow the build, I installed it in a directory tree for chroot use and have "kyua test -k /usr/tests/Kyuafile" running. I see evidence of various examples of one type of undefined behavior: "applying zer

FYI: An example ASAN failure report during kyua test -k /usr/tests/Kyuafile

Having done a buildworld with both WITH_ASAN= and WITH_UBSAN= after finding what to control to allow the build, I installed it in a directory tree for chroot use and have "kyua test -k /usr/tests/Kyuafile" running. I see evidence of one AddressSanitizer report. (kyua is still running.) The conte