Thank you. I'm looking forward to a clean build on the next release. ___________________________________________ Mark C Edwards Chief Scientist, C2 Systems Engineering & Integration 779 Monika Ct Chubbuck, ID 83202 mark.c.edwa...@leidos.com Mobile: 208-241-7982
-----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp Sent: Friday, December 15, 2017 9:42 PM To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Cc: sqlite-...@mailinglists.sqlite.org Subject: EXTERNAL: Re: [sqlite] Possibly uninitialized variables...compile time error On 12/15/17, Edwards, Mark C. <mark.c.edwa...@leidos.com> wrote: > sqlite3.c(167291): error C4703: potentially uninitialized local > pointer variable 'pNode' used > sqlite3.c(168154): error C4703: potentially uninitialized local > pointer variable 'pRoot' used > sqlite3.c(168160): error C4703: potentially uninitialized local > pointer variable 'pChild' used All these warnings are false positives. The variables are initialized by prior calls to the nodeAcquire() function. The problem is that nodeAcquire() does not necessarily initialize the variables, but if it does not, it returns a result code other than SQLITE_OK, and in those cases, the code that uses the variables that nodeAcquire() was suppose to have initialized is never reached. Thus there is no possibility of using an uninitialized variable. However, the code in question is not on a critical path. Hence, I have now added extra (unnecessary) local variable initializations in the relevant RTree indexing routines so that these warnings should now be suppressed. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
