Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #2502: PQclear: "invalid next size"
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "J. R. Fisher" <psql(at)jeffryfisher(dot)net>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #2502: PQclear: "invalid next size"
- Date: Thu, 29 Jun 2006 10:04:11 -0400
"J. R. Fisher" <psql(at)jeffryfisher(dot)net> writes: > *** glibc detected *** free(): invalid next size (normal): 0x08068ab0 Sounds like a memory clobber. The odds are extremely high that the clobber is in your own code, not libpq. If nothing else comes to mind, you could probably use ElectricFence or some other debugging-malloc package to help find the problem. regards, tom lane
- References:
- BUG #2502: PQclear: "invalid next size"
- From: J. R. Fisher
- BUG #2502: PQclear: "invalid next size"
- Prev by Date: Re: BUG #2503: Query results differ based on record count of unrelated table.
- Next by Date: BUG #2506: hash index
- Previous by thread: BUG #2502: PQclear: "invalid next size"
- Next by thread: BUG #2503: Query results differ based on record count of unrelated table.
- Indexes: