Re: Clang 3.3 Analyzer Results - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Clang 3.3 Analyzer Results
Date
Msg-id 20131113001108.GA16066@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Clang 3.3 Analyzer Results  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: Clang 3.3 Analyzer Results  (Jeffrey Walton <noloader@gmail.com>)
List pgsql-hackers
Kevin Grittner escribió:

> These both seemed legitimate to me.  Patch attached.  Any
> objections to applying it?  I realize the memory leak is a tiny one
> in the regression testing code, so it could never amount to enough
> to matter; but it seems worth fixing just to avoid noise in code
> analyzers.

We have marked a large number of memory leak reports by Coverity in
initdb and other short-lived programs as false positive, on the grounds
that there's no point in freeing memory in a program that's about to
terminate anyway.  I'm not saying I agree necessarily with that POV, but
if we take that stance then there's similarly no point in fixing this
leak in the regression test code, is there?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andreas
Date:
Subject: Re: Relax table alias conflict rule in 9.3?
Next
From: Jeffrey Walton
Date:
Subject: Re: Clang 3.3 Analyzer Results