From: Sam James <sam@gentoo.org>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: "David Malcolm" <dmalcolm@redhat.com>, GCC <gcc@gcc.gnu.org>,
"Iker Pedrosa" <ipedrosa@redhat.com>,
"Florian Weimer" <fweimer@redhat.com>,
"Paul Eggert" <eggert@cs.ucla.edu>,
"Michael Kerrisk" <mtk.manpages@gmail.com>,
"Martin Uecker" <uecker@tugraz.at>,
"Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>,
"Siddhesh Poyarekar" <siddhesh@sourceware.org>
Subject: Re: Missed warning (-Wuse-after-free)
Date: Fri, 17 Feb 2023 01:56:40 +0000 [thread overview]
Message-ID: <393614CB-C088-4793-A395-4BB9F9F48CE4@gentoo.org> (raw)
In-Reply-To: <7ef1efd4-66a1-51ca-a140-c3fc7b6c077f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
> On 17 Feb 2023, at 01:05, Alejandro Colomar via Gcc <gcc@gcc.gnu.org> wrote:
>
> On 2/17/23 02:04, Alejandro Colomar wrote:
>> [CC: Added those who contributed to the discussion in linux-man@,
>> and also the authors of N2861 for C2x]
>
> [...]
>
>>
>> There was a discussion in linux-man@ some years ago, which now I realize it
>> didn't end up being applied (I thought we had applied a patch, but it seems we
>> didn't). I'll check if we still need such a patch (and I guess we do, since
>> we're having this conversation).
>
> I forgot to link:
> <https://lore.kernel.org/linux-man/87lf4im6sf.fsf@oldenburg.str.redhat.com/T/>
>
See also https://siddhesh.in/posts/that-is-not-a-number-that-is-a-freed-object.html.
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2023-02-17 1:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 14:35 Alejandro Colomar
2023-02-16 15:15 ` David Malcolm
2023-02-17 1:04 ` Alejandro Colomar
2023-02-17 1:05 ` Alejandro Colomar
2023-02-17 1:56 ` Sam James [this message]
2023-02-17 8:12 ` Martin Uecker
2023-02-17 11:35 ` Alejandro Colomar
2023-02-17 13:34 ` Andreas Schwab
2023-02-17 13:48 ` Martin Uecker
2023-02-23 19:23 ` Alex Colomar
2023-02-23 19:57 ` Martin Uecker
2023-02-24 0:02 ` Alex Colomar
2023-02-24 1:21 ` Serge E. Hallyn
2023-02-24 1:42 ` Alex Colomar
2023-02-24 3:01 ` Peter Lafreniere
2023-02-24 8:52 ` Martin Uecker
2023-02-24 8:43 ` Martin Uecker
2023-02-24 16:10 ` Serge E. Hallyn
2023-02-24 8:36 ` Martin Uecker
2023-02-24 16:01 ` Serge E. Hallyn
2023-02-24 16:37 ` Martin Uecker
2023-02-17 3:48 ` Siddhesh Poyarekar
2023-02-17 11:22 ` Alejandro Colomar
2023-02-17 13:38 ` Siddhesh Poyarekar
2023-02-17 14:01 ` Mark Wielaard
2023-02-17 14:06 ` Siddhesh Poyarekar
2023-02-17 21:20 ` [PATCH] Make -Wuse-after-free=3 the default one in -Wall Alejandro Colomar
2023-02-17 21:39 ` Siddhesh Poyarekar
2023-02-17 21:41 ` Siddhesh Poyarekar
2023-02-17 22:58 ` Alejandro Colomar
2023-02-17 23:03 ` Siddhesh Poyarekar
2023-02-17 11:24 ` Missed warning (-Wuse-after-free) Jonathan Wakely
2023-02-17 11:43 ` Alejandro Colomar
2023-02-17 12:04 ` Jonathan Wakely
2023-02-17 12:53 ` Siddhesh Poyarekar
2023-02-17 14:10 ` Jonathan Wakely
2023-02-17 13:44 ` David Malcolm
2023-02-17 14:01 ` Siddhesh Poyarekar
2023-02-17 8:49 ` Yann Droneaud
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=393614CB-C088-4793-A395-4BB9F9F48CE4@gentoo.org \
--to=sam@gentoo.org \
--cc=alx.manpages@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ipedrosa@redhat.com \
--cc=jens.gustedt@inria.fr \
--cc=mtk.manpages@gmail.com \
--cc=siddhesh@sourceware.org \
--cc=uecker@tugraz.at \
/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).