| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: memory bug debugging |
| Date: | 2005-10-04 12:12:05 |
| Message-ID: | 20051004121143.GE17589@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 04, 2005 at 01:11:41PM +0200, Markus Schiltknecht wrote:
> Hello hackers,
>
> I'm fiddling around with the backend and have created a memory bug. I
> guess I'm overriding a palloced chunk, but can't figure out where.
There are some defines (MEMORY_CONTEXT_CHECKING and
CLOBBER_FREED_MEMORY) which can help find leaks. Valgrind works too,
with a bit of attention. I was going to add some directives to allow
Valgrind to handle PostgreSQL's memory allocator, but have got there
yet.
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-10-04 12:24:46 | Re: [PERFORM] A Better External Sort? |
| Previous Message | Simon Riggs | 2005-10-04 11:24:54 | Re: [PERFORM] A Better External Sort? |