Re: BUG #15540: Use after release in ExecuteTruncateGuts - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15540: Use after release in ExecuteTruncateGuts
Date
Msg-id 20181209022024.GD1833@paquier.xyz
Whole thread Raw
In response to Re: BUG #15540: Use after release in ExecuteTruncateGuts  (PanBian <bianpan2016@163.com>)
List pgsql-bugs
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

Attachment

pgsql-bugs by date:

Previous
From: PanBian
Date:
Subject: Re: BUG #15540: Use after release in ExecuteTruncateGuts
Next
From: PG Bug reporting form
Date:
Subject: BUG #15544: Unexpected: "Returned record type does not match expectedrecord type" after ALTER TABLE