Re: [CHECKER] 9 potential out-of-bounds array access errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Yichen Xie" <yxie(at)cs(dot)stanford(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org, mc(at)cs(dot)stanford(dot)edu
Subject: Re: [CHECKER] 9 potential out-of-bounds array access errors
Date: 2003-01-28 23:16:58
Message-ID: 4825.1043795818@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Yichen Xie" <yxie(at)cs(dot)stanford(dot)edu> writes:
> 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.

This looks like great stuff --- I haven't read through all of them, but
at least the first couple look like genuine bugs. I'm a little
suspicious of the tool's coverage though. For example, in
src/backend/utils/mb/conversion_procs/euc_tw_and_big5/big5.c,
why'd it flag only one of the two loops that use the same incorrect
limit for scanning b1c4[][] ?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Yichen Xie 2003-01-28 23:34:38 Re: [CHECKER] 9 potential out-of-bounds array access errors
Previous Message Tom Lane 2003-01-28 23:03:03 Re: pgtcl combined with view with certain insert/update-rules => crash