From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Rogers <temp6453@hotmail.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-php@postgresql.org
Cc: pgsql-bugs@postgresql.org
Subject: Re: PostgreSQL / PHP Overrun Error
Date: Wed, 26 Sep 2001 12:23:02 -0400
Message-ID: <1119.1001521382@sss.pgh.pa.us> (raw)
In-Reply-To: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com>
References: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com>
"Mike Rogers" <temp6453@hotmail.com> 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
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-php@postgresql.org
Cc: tgl@sss.pgh.pa.us, temp6453@hotmail.com, pgsql-hackers@postgresql.org, pgsql-bugs@postgresql.org
Subject: Re: PostgreSQL / PHP Overrun Error
In-Reply-To: <1119.1001521382@sss.pgh.pa.us>
References: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com> <1119.1001521382@sss.pgh.pa.us>
* 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