| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Jack Orenstein <jao(at)geophile(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Finding memory corruption in an extension |
| Date: | 2021-01-08 18:28:45 |
| Message-ID: | 326715.1610130525@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> pá 8. 1. 2021 v 18:48 odesílatel Jack Orenstein <jao(at)geophile(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raf | 2021-01-08 21:16:01 | Re: How to keep format of views source code as entered? |
| Previous Message | Pavel Stehule | 2021-01-08 17:53:52 | Re: Finding memory corruption in an extension |