> We are a group of Stanford researchers, and we've recently developed a > tool that detects potential out-of-bounds array accesses and buffer > overruns. Here are 9 potential bugs we've found on postgresql 7.3.1. > We've been checking linux for a few years, and we're interested in > expanding to other system software as well. Let us know if you guys are > interested in bug reports like this. Confirmation and comments will be > appreciated.
Thanks. I have confirmed that at least following reports are correct. Will fix them. > [BUG] "i" can go up to 13 > X [FALSE] > X [UNKNOWN] > X [BROKE] > X [SKIP] > /u2/yxie/postgresql-7.3.1/src/backend/utils/mb/conversion_procs/euc_tw_a > nd_big5/big5.c:364:CNStoBIG5: ERROR:BUFFER:364:364:Array bounds error v > [BUG] "i" can go up to 13 > X [FALSE] > X [UNKNOWN] > X [BROKE] > X [SKIP] > /u2/yxie/postgresql-7.3.1/src/backend/utils/mb/conversion_procs/euc_tw_a > nd_big5/big5.c:371:CNStoBIG5: ERROR:BUFFER:371:371:Array bounds error -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
