From: | "Dave Potts" <dave(dot)potts(at)pinan(dot)co(dot)uk> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | debugging postgres server memory checker |
Date: | 2012-02-29 07:59:38 |
Message-ID: | e080341a98f5a982c9a19c1fcff78a5d.squirrel@dp2642.f9.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
hi List,
As a result of writing a C 'postgres' function, I have a memory
corruption problem. Something is either being free twice or I am
accessing beyond the data structure and corrupting the malloc/free/sbrk
memory pool.
My attempts to memory support in glibc, that been stopped because
something seems to clear the envron before the postgres/postmaster program
is started(well ps does not report an envronment setting for this process)
Memory checking programs such as valgrind want direct control over the
postgres/postmaster process, ie they must fork the process and not the
postgres startup script from /etc/rc2.d
Q. How do inoke the postgres startup in such a way that my current
terminal becomes the controling terminal for the postgres/postmaster
process?
I do not want to run the postgres/postmaster program as a background
deamin style process.
Thanks in advance
Dave.
--
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Angelico | 2012-02-29 08:32:49 | Re: what Linux to run |
Previous Message | Durumdara | 2012-02-29 07:18:19 | Re: Correct way for locking a row for long time without blocking another transactions (=nowait)? |