public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/178] Please add strlcpy and strlcat (attached) Date: Wed, 14 Jun 2023 16:43:27 +0000 [thread overview] Message-ID: <bug-178-131-1F0FxFjyv4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-178-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=178 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.38 Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #8 from Florian Weimer <fweimer at redhat dot com> --- Fixed for 2.38 via: commit 454a20c8756c9c1d55419153255fc7692b3d2199 Author: Florian Weimer <fweimer@redhat.com> Date: Wed Jun 14 18:10:08 2023 +0200 Implement strlcpy and strlcat [BZ #178] These functions are about to be added to POSIX, under Austin Group issue 986. The fortified strlcat implementation does not raise SIGABRT if the destination buffer does not contain a null terminator, it just inherits the non-failing regular strlcat behavior. Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org> -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-06-14 16:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-178-131@http.sourceware.org/bugzilla/> 2014-09-08 11:52 ` [Bug libc/178] " fweimer at redhat dot com 2014-09-08 11:53 ` fweimer at redhat dot com 2014-10-23 0:57 ` thepouar at gmail dot com 2015-01-03 1:39 ` emaste at freebsd dot org 2015-08-27 22:02 ` [Bug string/178] " jsm28 at gcc dot gnu.org 2021-07-01 14:07 ` jscott at posteo dot net 2022-12-23 6:55 ` sam at gentoo dot org 2022-12-23 6:58 ` sam at gentoo dot org 2022-12-23 6:58 ` sam at gentoo dot org 2023-04-05 11:25 ` fweimer at redhat dot com 2023-06-14 16:43 ` fweimer at redhat dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-178-131-1F0FxFjyv4@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).