| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | greimel(at)ing(dot)iac(dot)es (Robert Greimel) |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: 7.4RC1 et al: cannot find block containing chunk |
| Date: | 2003-11-09 23:25:38 |
| Message-ID: | 10136.1068420338@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
greimel(at)ing(dot)iac(dot)es (Robert Greimel) writes:
> using PostgreSQL-7.2.2 and several user defined C function - dynamically loaded
> from one .so file - I (sometimes) see the following error message doing the
> following query:
> ERROR: AllocSetFree: cannot find block containing chunk 0x83a5300
This indicates that somebody is pfree'ing a pointer that did not come
from palloc, or possibly pfree'ing the same pointer twice. It could be
that the bad pfree is the indirect result of an earlier memory clobber,
too.
Given that you are using user-defined C functions it seems highly likely
that the bug is in your code and not Postgres. If you can reproduce the
bug without any of your own C functions having been executed, please
send along a script that does it ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2003-11-10 00:24:46 | Re: Autocomplete <TAB> on Postgres7.4beta5 not working? |
| Previous Message | Robert Greimel | 2003-11-09 22:33:48 | Re: 7.4RC1 et al: cannot find block containing chunk |