Well it really isn't your code (true), but the only thing that is changed is
the 7.0-7.1- Was a data length changed on the return or something that
could affect this?
--
Mike
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mike Rogers" <temp6453(at)hotmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>; <pgsql-php(at)postgresql(dot)org>;
<pgsql-bugs(at)postgresql(dot)org>
Sent: Wednesday, September 26, 2001 1:23 PM
Subject: Re: [BUGS] PostgreSQL / PHP Overrun Error
> "Mike Rogers" <temp6453(at)hotmail(dot)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
>