[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: RE: BoundsChecker
- From: Jim Mathies <Jim@...>
- Date: Mon, 11 Sep 2000 12:32:23 -0700
I use bc 6.2 (not 6.5) - i have no trouble with lua 3.2.
-----Original Message-----
From: erik@hougaard.com [mailto:erik@hougaard.com]
Sent: Monday, September 11, 2000 7:36 AM
To: Multiple recipients of list
Subject: Re: BoundsChecker
It seem that it is only when the insert_s() is called from LoadTString
from
lundump.c ?
/Erik
----- Original Message -----
From: "Roberto Ierusalimschy" <roberto@inf.puc-rio.br>
To: "Multiple recipients of list" <lua-l@tecgraf.puc-rio.br>
Sent: Monday, September 11, 2000 4:28 PM
Subject: Re: BoundsChecker
I have never used BoundChecker, but we frequently run Purify over the
code,
without any warning. However, lstring.c does a trick that may bother
BoundChecker: It defines a struct that ends with «char str[1]», and
mallocs
it with a bigger size, to fit a string into this field. Maybe
BoundChecker
trusts this faked 1 and complains about that.
(It seems that the new ANSI C will have a feature for that.)
-- Roberto
