| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | PanBian <bianpan2016(at)163(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15540: Use after release in ExecuteTruncateGuts |
| Date: | 2018-12-09 02:20:24 |
| Message-ID: | 20181209022024.GD1833@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-12-09 02:30:07 | BUG #15544: Unexpected: "Returned record type does not match expected record type" after ALTER TABLE |
| Previous Message | PanBian | 2018-12-09 00:56:17 | Re: BUG #15540: Use after release in ExecuteTruncateGuts |