corrupted double-linked list
in [PgSql]
|
Prev: [HACKERS] integer input functions : interesting limit behaviour
Next: WIP: generalized index constraints
From: Tom Lane on 9 Sep 2009 13:47 Maarten =?ISO-8859-1?Q?Foqu=E9?= <maarten.foque(a)edchq.com> writes: > The program crashes on PQclear(resu) with the following: > *** glibc detected *** ./incident_relay: corrupted double-linked list: > 0x09c459c8 *** This looks like a memory-stomp type of bug. There's no reason to assume that PQclear is the cause; it's more likely the victim of a stomp that occurred sometime earlier. I'd suggest running the app under valgrind or electric fence or some other memory-overrun-catcher. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Maarten =?ISO-8859-1?Q?Foqu=E9?= on 10 Sep 2009 03:45
Thanks, you were right on. regards, Maarten On Wed, 2009-09-09 at 13:47 -0400, Tom Lane wrote: > Maarten =?ISO-8859-1?Q?Foqu=E9?= <maarten.foque(a)edchq.com> writes: > > The program crashes on PQclear(resu) with the following: > > *** glibc detected *** ./incident_relay: corrupted double-linked list: > > 0x09c459c8 *** > > This looks like a memory-stomp type of bug. There's no reason to assume > that PQclear is the cause; it's more likely the victim of a stomp that > occurred sometime earlier. I'd suggest running the app under valgrind > or electric fence or some other memory-overrun-catcher. > > regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |