Re: Finding memory corruption in an extension - Mailing list pgsql-general

From Tom Lane
Subject Re: Finding memory corruption in an extension
Date
Msg-id 326715.1610130525@sss.pgh.pa.us
Whole thread Raw
In response to Re: Finding memory corruption in an extension  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
Pavel Stehule <pavel.stehule@gmail.com> writes:
> pá 8. 1. 2021 v 18:48 odesílatel Jack Orenstein <jao@geophile.com> napsal:
>> I'm interested in advice on how to go about hunting down my problem.
>> Something along the lines of a debugging malloc, or valgrind, for Postgres.

> The basic feature is using postgres compiled with --enable-cassert flag. It
> does lot of checks of memory corruptions

Yeah, you should absolutely use --enable-cassert when working on C code.

If you need valgrind, there's advice about how to run it at

https://wiki.postgresql.org/wiki/Valgrind

            regards, tom lane



pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Finding memory corruption in an extension
Next
From: raf
Date:
Subject: Re: How to keep format of views source code as entered?