On Thu, Jun 29, 2017 at 9:12 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Merlin Moncure <mmonc...@gmail.com> writes: >> On Thu, Jun 29, 2017 at 8:23 AM, Michal Novotny >> <michal.novo...@greycortex.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
