Re: Running BoundsChecker on 5.0.2

[Michael Abbott <mabster@...>]

On Sat, 2006-02-25 at 22:30 +0100, Mike Pall wrote:
> Hi,
> 
> Dario Accornero wrote:
> > For instance, when calling lua_open() for the very first time, 
> > BoundsChecker reports an uninitialized memory read in luaH_new (line 330 of 
> > ltable):
> > 
> >    t->metatable = hvalue(defaultmeta(L));
> > 
> > Several similar errors are reported in luaK_posfix() (line 653 of lcode) 
> > and other lines of the same module; in luaV_execute(), lines 496 and others 
> > of lvm, BoundsChecker also reports some pointer arithmetic range errors.
> 
> None of these are errors. This is just copying uninitialized
> memory. Either without using it or by overwriting it later with
> valid data.

Just for interest sake, how much memory of this type is getting copied
around?  I would have though that copying around data that just gets
overwritten again / never used would have been a bad sign (from an
efficiency standpoint)?

- Mab