[Bug 294881] test failures with FORTIFY_SOURCE=2
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294881] test failures with FORTIFY_SOURCE=2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294881] test failures with FORTIFY_SOURCE=2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294881] test failures with FORTIFY_SOURCE=2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294881] test failures with FORTIFY_SOURCE=2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 294881] test failures with FORTIFY_SOURCE=2"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 29 Apr 2026 20:33:02 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294881
Bug ID: 294881
Summary: test failures with FORTIFY_SOURCE=2
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: tests
Assignee: testing@FreeBSD.org
Reporter: markj@FreeBSD.org
I built a FreeBSD image with FORTIFY_SOURCE=2 and ran the regression test
suite. There are some test failures:
lib/libc/stdio/gets_s_test:n_gt_rmax -> broken: Empty test result or no new
line [0.345s]
lib/libc/stdio/gets_s_test:n_gt_rmax_handler -> broken: Empty test result or
no new line [0.059s]
lib/libc/sys/getgroups_test:getgroups_err -> broken: Empty test result or no
new line [0.065s]
sys/audit/network:recvmsg_failure -> broken: Empty test result or no new line
[0.008s]
All of them are tests which make sure that various libc functions return an
error when given invalid parameters, but SSP checks turn that into a fatal
abort.
Is that a bug in the FORTIFY_SOURCE integration? Should we build tests with
FORTIFY_SOURCE enabled at all?
--
You are receiving this mail because:
You are the assignee for the bug.