Re: [BUGS] Segmentation fault in libpq

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michal Novotny <michal(dot)novotny(at)greycortex(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUGS] Segmentation fault in libpq
Date: 2017-06-29 14:30:38
Message-ID: CAHyXU0yjj49MzD5Sei3g4ihL_gzVDxFhJt2Qs9NfgYkaJEw4hA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Jun 29, 2017 at 9:12 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> On Thu, Jun 29, 2017 at 8:23 AM, Michal Novotny
>> <michal(dot)novotny(at)greycortex(dot)com> wrote:
>>> Could you please help me based on information provided above?
>
>> You might want to run your code through some analysis tools (for
>> example, valgrind).
>
> valgrind is not a perfect tool for finding that kind of problem,
> especially if you can't reproduce the crash reliably; but at least
> valgrind is readily available and easy to use, so you might as
> well start there and see if it finds anything. If you have access
> to any sort of static analysis tool (eg, Coverity), that might be
> more likely to help. Or you could fall back on manual code
> auditing, if the program isn't very big.

clang static analyzer is another good tool to check out

https://clang-analyzer.llvm.org/

merlin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message skoposov 2017-06-29 16:16:37 BUG #14722: Segfault in tuplesort_heap_siftup, 32 bit overflow
Previous Message Tom Lane 2017-06-29 14:12:56 Re: [BUGS] Segmentation fault in libpq

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrien Nayrat 2017-06-29 16:30:05 Re: Dumping database creation options and ACLs
Previous Message Tom Lane 2017-06-29 14:12:56 Re: [BUGS] Segmentation fault in libpq