[HACKERS] [bug fix] Trivial ecpg bug which can cause memory overrun - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject [HACKERS] [bug fix] Trivial ecpg bug which can cause memory overrun
Date
Msg-id 0A3221C70F24FB45833433255569204D1F66B412@G01JPEXMBYT05
Whole thread Raw
Responses Re: [HACKERS] [bug fix] Trivial ecpg bug which can cause memoryoverrun  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
Hello,

While investigating some other issue, we found a trivial bug of ecpg.  The attached is a fix for that.

If you specify an input file which ends with "." (e.g. run "ecpg file."), ecpg writes one byte past the end of the
allocatedmemory.
 

In addition, the following statement is misleading.  Some people may think that file.ec.c will be converted to a.ec.c.
Butthe actual behavior is that it is converted to file.c.  So I clarified the paragraph a bit.
 

"If the extension of the input file is not .pgc, then the output file name is computed by appending .c to the full file
name."

Regards
Takayuki Tsunakawa


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: [HACKERS] Getting rid of "unknown error" in dblink andpostgres_fdw
Next
From: Kuntal Ghosh
Date:
Subject: Re: [HACKERS] WAL consistency check facility