Re: BUG #15540: Use after release in ExecuteTruncateGuts
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: PanBian <bianpan2016@163.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Date: 2018-12-09T02:20:24Z
Lists: 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
Commits
-
Fix misapplication of pgstat_count_truncate to wrong relation.
- aedd3d4dbd6e 11.2 landed
- 54f24ab76ded 10.7 landed
- 4d5cfb91156d 9.5.16 landed
- 078303f79b51 9.6.12 landed
- 5deadfef2827 12.0 landed