From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | marcelo Cortez <jmdc_marcelo(at)yahoo(dot)com(dot)ar> |
Cc: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: double free corruption? |
Date: | 2007-12-28 16:49:42 |
Message-ID: | 4020.1198860582@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
marcelo Cortez <jmdc_marcelo(at)yahoo(dot)com(dot)ar> writes:
> sorry i forgot to mention
> i'm developing one c external program, may be fault is
> my code , but surprise to me the message, what bad
> practice generate this behavior?
> fail seems to be not to reproducible all times,
> i'm using beta3 version, it's this important?
What it looks like to me is something clobbering memory, eg writing more
data into a palloc'd memory chunk than will fit; which results in
overwriting malloc's own data structures, causing malloc to complain
when it notices.
Whether it's your bug or something wrong in the beta is hard to say.
> pd: gdb can help? ( for debugging my own code)
--enable-cassert would probably help more, since it would turn on some
clobber-detection support in PG.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Harrison | 2007-12-28 17:06:42 | Re: Any big slony and WAL shipping users? |
Previous Message | Gauthier, Dave | 2007-12-28 16:46:14 | default superuser |