Re: Coverity Open Source Defect Scan of PostgreSQL

Поиск
Список
Период
Сортировка
От Ben Chelf
Тема Re: Coverity Open Source Defect Scan of PostgreSQL
Дата
Msg-id 440F1258.5040507@coverity.com
обсуждение исходный текст
Ответ на Re: Coverity Open Source Defect Scan of PostgreSQL  (Martijn van Oosterhout <kleptog@svana.org>)
Ответы Re: Coverity Open Source Defect Scan of PostgreSQL  (Josh Berkus <josh@agliodbs.com>)
Re: Coverity Open Source Defect Scan of PostgreSQL  (Greg Stark <gsstark@mit.edu>)
Список pgsql-hackers

Martijn van Oosterhout wrote:
> On Tue, Mar 07, 2006 at 05:39:18PM -0500, Tom Lane wrote:
> 
>>Martijn van Oosterhout <kleptog@svana.org> writes:
>>
>>>#ifdef STATIC_ANALYSIS
>>>#define ereport(elevel, rest)  \
>>>        (errstart(elevel, __FILE__, __LINE__, PG_FUNCNAME_MACRO) ? \
>>>         (errfinish rest) : (void) 0), (elevel >= ERROR ? exit(0) : 0)
>>>#else
>>>/* Normal def */
>>>#endif
>>
>>Hmm, neat idea ... though I wonder whether either gcc or Coverity's tool
>>is smart enough to draw the right conclusions from a conditional exit()
>>call ...
> 

As for Coverity, if the elevel that's passed to the ereport is really a 
constant, the above #ifdef should absolutely do the trick for us so we 
know to stop analyzing on that path...Let me know if it doesn't actually 
do that ;)

-ben



В списке pgsql-hackers по дате отправления:

Предыдущее
От: etmorelli
Дата:
Сообщение: Re: Problemas with gram.y
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Merge algorithms for large numbers of "tapes"