public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28746] New: _FORTIFY_SOURCE does not work for stpcpy Date: Tue, 04 Jan 2022 19:27:30 +0000 [thread overview] Message-ID: <bug-28746-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28746 Bug ID: 28746 Summary: _FORTIFY_SOURCE does not work for stpcpy Product: glibc Version: 2.35 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: siddhesh at sourceware dot org Reporter: siddhesh at sourceware dot org CC: drepper.fsp at gmail dot com Target Milestone: --- The definition for the fortified version of stpcpy and a few other functions are incorrectly under __USE_GNU when they should be under __USE_XOPEN2K8 because of which, they don't get fortified when _GNU_SOURCE is not defined. See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89748 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-01-04 19:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-04 19:27 siddhesh at sourceware dot org [this message] 2022-01-04 19:27 ` [Bug libc/28746] " siddhesh at sourceware dot org 2022-01-12 18:06 ` cvs-commit at gcc dot gnu.org 2022-01-12 18:08 ` siddhesh at sourceware dot org 2022-03-11 15:12 ` cvs-commit at gcc dot gnu.org
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-28746-131@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).