psql Segfaults shortly after doing variable substitution - Mailing list pgsql-patches

From William K. Volkman
Subject psql Segfaults shortly after doing variable substitution
Date
Msg-id 1023122945.16199.7.camel@wkv2
Whole thread Raw
Responses Re: psql Segfaults shortly after doing variable substitution  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: psql Segfaults shortly after doing variable substitution  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Noted with versions 7.0.3, 7.1.3, and 7.2.1:

The psql interpreter becomes unstable if variable substitutions
are used.  The debugger GDB was unable to help however mpatrol
reports that the sprintf at mainloop.c:389 is steping one byte
farther than the allocation.

Patch file attached.

Cheers,
William.



--- postgresql-7.1.3/src/bin/psql/mainloop.c~    Mon Mar 26 08:18:51 2001
+++ postgresql-7.1.3/src/bin/psql/mainloop.c    Tue May 28 15:00:12 2002
@@ -379,7 +379,8 @@
                 {
                     out_length = strlen(value);

-                    new = malloc(len + out_length - (1 + in_length) + 1);
+                    /* Allow for 'after' character also 2002-05-27 */
+                    new = malloc(len + out_length - (1 + in_length) + 1 + 1);
                     if (!new)
                     {
                         psql_error("out of memory\n");

pgsql-patches by date:

Previous
From: Ingo Luetkebohle
Date:
Subject: PostgreSQL support for MiddleKit
Next
From: Bruce Momjian
Date:
Subject: Re: Python DB API (pgdb.py) patch