From: Michael Paquier <michael@paquier.xyz>
To: PanBian <bianpan2016@163.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15540: Use after release in ExecuteTruncateGuts
Date: Sun, 9 Dec 2018 11:20:24 +0900
Message-ID: <20181209022024.GD1833@paquier.xyz> (raw)
In-Reply-To: <20181209005617.GA65607@bp>
References: <15540-01078812338195c0@postgresql.org>
<31125.1544198945@sss.pgh.pa.us>
<20181209005617.GA65607@bp>
On Sun, Dec 09, 2018 at 08:56:17AM +0800, PanBian wrote:
> Yes. I write a static analysis tool. It can find functions that release
> memory or other resources. Let's call them free-like functions. With such
> free-like functions, the tool then performs data flow analysis to find
> use-after-free bugs. Of course, we can feed those free-like functions to
> other static analyzers such as Coverity. I believe it will work too.
Interesting. Did you release this stuff in the open? I could be very
interesting to get that plugged in more easily with Postgres. Community
runs Coverity as well. The reports are not public still if that helps
in reporting real issues and not only false positives that would be
nice.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../20181209022024.GD1833@paquier.xyz/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, bianpan2016@163.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15540: Use after release in ExecuteTruncateGuts
In-Reply-To: <20181209022024.GD1833@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox