pg.ddx.io pgsql-testers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Paul Anderson <paul.a@pnlassociates.com>
To: pgsql-testers@postgresql.org
Cc: Paul B. Anderson <paul.a@pnlassociates.com>
Subject: Glibc error using ecpg
Date: Fri, 07 May 2010 09:06:10 -0400
Message-ID: <4BE41042.2040006@pnlassociates.com> (raw )
I just received this error from a program I'm testing with postgresql
9. It is an operational program under 8.1.
From the debug output, I think I am getting the following error on the
statement
EXEC SQL CLOSE FROMID;
with the situation being that the cursor is on a result set with zero rows.
Here is the error info:
*** glibc detected *** mainprog: double free or corruption (!prev):
0x09ad5be8 ***
======= Backtrace: =========
/lib/i686/nosegneg/libc.so.6[0x6e51e5]
/lib/i686/nosegneg/libc.so.6(cfree+0x59)[0x6e5629]
mainprog[0x804ab53]
mainprog[0x804a375]
/lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc)[0x690e9c]
mainprog[0x8048a71]
======= Memory map: ========
00110000-0011d000 r-xp 00000000 fd:00 2019722
/usr/local/pgsql/lib/libpgtypes.so.3.1
0011d000-0011f000 rwxp 0000c000 fd:00 2019722
/usr/local/pgsql/lib/libpgtypes.so.3.1
00275000-00290000 r-xp 00000000 fd:00 2019039
/usr/local/pgsql/lib/libpq.so.5.3
00290000-00291000 rwxp 0001b000 fd:00 2019039
/usr/local/pgsql/lib/libpq.so.5.3
004f4000-004fd000 r-xp 00000000 fd:00 1659894 /lib/libnss_files-2.5.so
004fd000-004fe000 r-xp 00008000 fd:00 1659894 /lib/libnss_files-2.5.so
004fe000-004ff000 rwxp 00009000 fd:00 1659894 /lib/libnss_files-2.5.so
0065d000-00677000 r-xp 00000000 fd:00 1334309 /lib/ld-2.5.so
00677000-00678000 r-xp 00019000 fd:00 1334309 /lib/ld-2.5.so
00678000-00679000 rwxp 0001a000 fd:00 1334309 /lib/ld-2.5.so
0067b000-007bd000 r-xp 00000000 fd:00 1366888
/lib/i686/nosegneg/libc-2.5.so
007bd000-007be000 --xp 00142000 fd:00 1366888
/lib/i686/nosegneg/libc-2.5.so
007be000-007c0000 r-xp 00142000 fd:00 1366888
/lib/i686/nosegneg/libc-2.5.so
007c0000-007c1000 rwxp 00144000 fd:00 1366888
/lib/i686/nosegneg/libc-2.5.so
007c1000-007c4000 rwxp 007c1000 00:00 0
007c6000-007eb000 r-xp 00000000 fd:00 1367136
/lib/i686/nosegneg/libm-2.5.so
007eb000-007ec000 r-xp 00024000 fd:00 1367136
/lib/i686/nosegneg/libm-2.5.so
007ec000-007ed000 rwxp 00025000 fd:00 1367136
/lib/i686/nosegneg/libm-2.5.so
007f5000-00809000 r-xp 00000000 fd:00 1366910
/lib/i686/nosegneg/libpthread-2.5.so
00809000-0080a000 r-xp 00013000 fd:00 1366910
/lib/i686/nosegneg/libpthread-2.5.so
0080a000-0080b000 rwxp 00014000 fd:00 1366910
/lib/i686/nosegneg/libpthread-2.5.so
0080b000-0080d000 rwxp 0080b000 00:00 0
0081e000-0081f000 r-xp 0081e000 00:00 0 [vdso]
008b8000-008c8000 r-xp 00000000 fd:00 2019731
/usr/local/pgsql/lib/libecpg.so.6.2
008c8000-008c9000 rwxp 0000f000 fd:00 2019731
/usr/local/pgsql/lib/libecpg.so.6.2
008c9000-00989000 rwxp 008c9000 00:00 0
0518c000-05197000 r-xp 00000000 fd:00 1334378
/lib/libgcc_s-4.1.2-20080825.so.1
05197000-05198000 rwxp 0000a000 fd:00 1334378
/lib/libgcc_s-4.1.2-20080825.so.1
0537a000-0545a000 r-xp 00000000 fd:00 1279105 /usr/lib/libstdc++.so.6.0.8
0545a000-0545e000 r-xp 000df000 fd:00 1279105 /usr/lib/libstdc++.so.6.0.8
0545e000-0545f000 rwxp 000e3000 fd:00 1279105 /usr/lib/libstdc++.so.6.0.8
0545f000-05465000 rwxp 0545f000 00:00 0
05584000-0558d000 r-xp 00000000 fd:00 1659825 /lib/libcrypt-2.5.so
0558d000-0558e000 r-xp 00008000 fd:00 1659825 /lib/libcrypt-2.5.so
0558e000-0558f000 rwxp 00009000 fd:00 1659825 /lib/libcrypt-2.5.so
0558f000-055b6000 rwxp 0558f000 00:00 0
08048000-08050000 r-xp 00000000 03:41 6455433
/app/new-mchs/MCHS/trunk/src/repository/sid-search/mainprog
08050000-08051000 rw-p 00008000 03:41 6455433
/app/new-mchs/MCHS/trunk/src/repository/sid-search/mainprog
09acc000-09aed000 rw-p 09acc000 00:00 0
b7f02000-b7f05000 rw-p b7f02000 00:00 0
b7f13000-b7f15000 rw-p b7f13000 00:00 0
bf870000-bf885000 rw-p bffea000 00:00 0 [stack]
Abort
view thread (6+ messages) latest in thread
Message-ID: <4BE41042.2040006@pnlassociates.com>
Permalink: ../4BE41042.2040006@pnlassociates.com/
Also on: postgresql.org/message-id/4BE41042.2040006@pnlassociates.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-testers@postgresql.org
Cc: paul.a@pnlassociates.com
Subject: Re: Glibc error using ecpg
In-Reply-To: <4BE41042.2040006@pnlassociates.com>
References: <4BE41042.2040006@pnlassociates.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox