public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/94169] warn for modifying getenv() result
Date: Mon, 16 Mar 2020 19:34:15 +0000	[thread overview]
Message-ID: <bug-94169-4-vFfXfkFCuN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94169-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94169

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Other C standard functions that return a pointer to an unmodifiable object:

  localeconv(), setlocale(), strerror()

In addition, stdin, stdout, and stderr could be marked as pointing to read-only
(although uses by standard library macros would have to be exempted).

and POSIX:

  ctermid()
  dlerror()
  getgrent()
  gethostent()
  getnetbyaddr(), getnetbyname(), getnetent()
  getprotbyname(), getprotbynumber(), getprotent()
  getpwent(), getpwnam(), getpwuid(),
  getservbyname(), getservbyport(), getservent()
  getutxent(), getutxid(), getutxline()
  getgrid(), getgrnam(), getlogin()
  getsubopt() (object pointed to by second argument)
  nl_langinfo()
  ptsname()
  readdir()
  strsignal()
  ttyname()

  parent reply	other threads:[~2020-03-16 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 16:12 [Bug middle-end/94169] New: " msebor at gcc dot gnu.org
2020-03-16 19:10 ` [Bug middle-end/94169] " msebor at gcc dot gnu.org
2020-03-16 19:34 ` msebor at gcc dot gnu.org [this message]
2020-10-19 20:47 ` dmalcolm at gcc dot gnu.org
2020-10-19 22:33 ` msebor 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-94169-4-vFfXfkFCuN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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: link
Be 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).