Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8QGNDh17167; Wed, 26 Sep 2001 12:23:13 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f8QGN2K01122; Wed, 26 Sep 2001 12:23:02 -0400 (EDT) To: "Mike Rogers" cc: pgsql-hackers@postgresql.org, pgsql-php@postgresql.org, pgsql-bugs@postgresql.org Subject: Re: PostgreSQL / PHP Overrun Error In-reply-to: References: Comments: In-reply-to "Mike Rogers" message dated "Wed, 26 Sep 2001 13:13:17 -0300" Date: Wed, 26 Sep 2001 12:23:02 -0400 Message-ID: <1119.1001521382@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200109/178 X-Sequence-Number: 2328 "Mike Rogers" writes: > This problem is of great concern to me and I have been working for days > trying to debug it myself and find other reports, with little success. The > line it claims to be failing on is PHP's ext/pgsql/pgsql.c on line 167 (by > what this claims) which is the following function [the > efree(PGG(last_notice)) line]. This isn't our code, so you'd likely have better luck complaining on some PHP-related list. But it looks to me like this code is simply trying to free any previous notice message before it stores the new one into PGG(last_notice) (whatever the heck that is). I'm guessing that that pointer is uninitialized or has been clobbered somehow. regards, tom lane