public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/28521] likely benign use-after-free instances in Glibc
Date: Fri, 12 Nov 2021 15:50:43 +0000	[thread overview]
Message-ID: <bug-28521-131-TcyyKyEWVn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28521-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28521

--- Comment #2 from Martin Sebor <msebor at gmail dot com> ---
The warning has three levels, with equality comparisons of indeterminate
pointers triggers being diagnosed only in level 3.

But remember, these are warnings, not hard errors: their purpose is to
highlight potentially risky (or undefined) code.  They don't make such code
impossible, just like the "change oil" light in your car doesn't keep you from
driving it.  How users choose to handle them is up to them.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-11-12 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 19:05 [Bug build/28521] New: " msebor at gmail dot com
2021-11-12 10:54 ` [Bug build/28521] " fweimer at redhat dot com
2021-11-12 15:50 ` msebor at gmail dot com [this message]
2022-01-12 17:16 ` msebor at gmail dot com

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-28521-131-TcyyKyEWVn@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: 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).