glibc/debug, branch masterFork of glibc for developmenthttps://git.zx2c4.com/glibc/atom/debug?h=master2024-05-14T10:55:06ZUnify output from backtrace_symbols_fd with backtrace_symbols (bug 31730)2024-05-14T10:55:06ZAndreas Schwabschwab@suse.de2024-05-13T10:35:48Zurn:sha1:ec6ed525f1aa24fd38ea5153e88d14d92d0d2f82string: Add hidden builtin definition for __strcpy_chk.2024-02-06T08:17:04ZStefan Lieblerstli@linux.ibm.com2024-02-05T13:22:06Zurn:sha1:fa3eb7d5e7d32ca1ad48b48a7eb6d15b8382c3a7
Otherwise on at least x86_64 and s390x there is an unwanted PLT entry
in libc.so when configured with --enable-fortify-source=3 and build
with -Os.
This is observed in elf/check-localplt
Extra PLT reference: libc.so: __strcpy_chk
The call to PLT entry is in inet/ruserpass.c.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
debug/getwd_chk.c: warning should be emitted for the __getwd_chk symbol.2024-01-12T14:21:26ZFrederic Cambusfred@statdns.com2023-12-05T11:23:07Zurn:sha1:9fd2ceb55de003c09c909103966db913319bcfdc
Otherwise the warning message for the getwd symbol ends up being duplicated.
Signed-off-by: Frederic Cambus <fred@statdns.com>
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
Update copyright dates not handled by scripts/update-copyrights2024-01-01T18:53:40ZPaul Eggerteggert@cs.ucla.edu2024-01-01T18:35:28Zurn:sha1:1059defeee95e28c65b266a55eba6d47d852026b
I've updated copyright dates in glibc for 2024. This is the patch for
the changes not generated by scripts/update-copyrights and subsequent
build / regeneration of generated files.
Update copyright dates with scripts/update-copyrights2024-01-01T18:53:40ZPaul Eggerteggert@cs.ucla.edu2024-01-01T18:12:26Zurn:sha1:dff8da6b3e89b986bb7f6b1ec18cf65d5972e307debug: Add fortify wprintf tests2023-12-29T13:57:27ZAdhemerval Zanellaadhemerval.zanella@linaro.org2023-12-21T18:59:19Zurn:sha1:a8a4c94ae9cefeeba72ca41364fcf684a64477bc
Similar to other printf-like ones. It requires to be in a different
process so we can change the orientation of stdout.
Checked on aarch64, armhf, x86_64, and i686.
debug: Add fortify syslog tests2023-12-29T13:57:03ZAdhemerval Zanellaadhemerval.zanella@linaro.org2023-12-21T18:59:18Zurn:sha1:446e2c935a174d33fa9974859628e3c44156bca9
It requires to be in a container tests to avoid logging bogus
information on the system. The syslog also requires to be checked in
a different process because the internal printf call will abort with
the internal syslog lock taken (which makes subsequent syslog calls
deadlock).
Checked on aarch64, armhf, x86_64, and i686.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
debug: Add fortify dprintf tests2023-12-29T13:57:03ZAdhemerval Zanellaadhemerval.zanella@linaro.org2023-12-21T18:59:17Zurn:sha1:121aad59dea8431cae5cd3efb6ba588d0ddc52b4
Similar to other printf-like ones.
Checked on aarch64, armhf, x86_64, and i686.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
debug: Increase tst-fortify checks for compiler without __va_arg_pack support2023-12-29T13:57:03ZAdhemerval Zanellaadhemerval.zanella@linaro.org2023-12-21T18:59:16Zurn:sha1:bf320000b47ce46aa6dbe1b7068e6539bf2df9bb
The fortify wrappers for varargs functions already add fallbacks to
builtins calls if __va_arg_pack is not supported.
Checked on aarch64, armhf, x86_64, and i686.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
debug: Adapt fortify tests to libsupport2023-12-29T13:57:03ZAdhemerval Zanellaadhemerval.zanella@linaro.org2023-12-21T18:59:15Zurn:sha1:9556acd249687ac562deb6309503165d66eb06fa
Checked on aarch64, armhf, x86_64, and i686.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>