Skip site navigation (1) Skip section navigation (2)

Re: BUG #2502: PQclear: "invalid next size"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "J(dot) R(dot) Fisher" <psql(at)jeffryfisher(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2502: PQclear: "invalid next size"
Date: 2006-06-29 14:04:11
Message-ID: 20267.1151589851@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"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

In response to

pgsql-bugs by date

Next:From: Wagner CiprianoDate: 2006-06-29 14:09:42
Subject: BUG #2506: hash index
Previous:From: Alvaro HerreraDate: 2006-06-29 13:56:16
Subject: Re: BUG #2503: Query results differ based on record count of unrelated table.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group