"Damian Slee" <[EMAIL PROTECTED]> wrote:
>
> I have done some testing with 3.2 and now 3.4, visual studio2003 and
> boundschecker (and XP).
Thank you for the report.
I have analyzed the errors reported by boundschecker and they
all appear to be false postives. The SQLite 3.4.0 code base
is correct in all cases and boundchecker is complaining about
problems that do not exist.
The following is typical:
>
> Dangling Pointer: Pointer 0x010D9250, allocated by HeapAlloc, has already
> been freed.
>
> Vdbe.c sqlite3VdbeExec Line 469
>
> if( p->magic!=VDBE_MAGIC_RUN ) return SQLITE_MISUSE;
> assert( db->magic==SQLITE_MAGIC_BUSY );
> [pTos = p->pTos;]
> if( p->rc==SQLITE_NOMEM ){
>
There are two pointers on the offending line: "p" and "pTos". The
p pointer appears to be valid. Otherwise, the "return SQLITE_MISUSE"
two lines above would have be taken. Or at worst, the dereference
of p two lines above should have triggered a similar error. So
apparently boundschecker is upset because SQLite is merely making
a copy pointer to previously freed memory. There really is no
harm in this. Nothing bad can happen unless the program actually
tries to dereference the pointer - which it never does.
--
D. Richard Hipp <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
