pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mike Rogers <temp6453@hotmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
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 13:28:49 -0300
Message-ID: <OE229OEUO0UiwiL4l4800002dbf@hotmail.com> (raw)
References: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com>
	<1119.1001521382@sss.pgh.pa.us>

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@sss.pgh.pa.us>
To: "Mike Rogers" <temp6453@hotmail.com>
Cc: <pgsql-hackers@postgresql.org>; <pgsql-php@postgresql.org>;
<pgsql-bugs@postgresql.org>
Sent: Wednesday, September 26, 2001 1:23 PM
Subject: Re: [BUGS] PostgreSQL / PHP Overrun Error


> "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
>



view thread (24+ messages)  latest in thread

Message-ID: <OE229OEUO0UiwiL4l4800002dbf@hotmail.com>
Permalink:  ../OE229OEUO0UiwiL4l4800002dbf@hotmail.com/
Also on:    postgresql.org/message-id/OE229OEUO0UiwiL4l4800002dbf@hotmail.com

 · 

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-php@postgresql.org
  Cc: temp6453@hotmail.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org, pgsql-bugs@postgresql.org
  Subject: Re: PostgreSQL / PHP Overrun Error
  In-Reply-To: <OE229OEUO0UiwiL4l4800002dbf@hotmail.com>
  References: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com> <1119.1001521382@sss.pgh.pa.us> <OE229OEUO0UiwiL4l4800002dbf@hotmail.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