[Python-checkins] r46936 - in python/trunk: Lib/sqlite3/test/regression.py Lib/sqlite3/test/types.py Lib/sqlite3/test/userfunctions.py Modules/_sqlite/connection.c Modules/_sqlite/cursor.c Modules/_sqlite/module.c Modules/_sqlite/module.h

Wed Jun 14 09:34:28 CEST 2006

On 6/13/06, Tim Peters <tim.peters at gmail.com> wrote:
> > Author: gerhard.haering
> > Date: Wed Jun 14 00:24:47 2006
> > New Revision: 46936
> >
> > Modified:
> > python/trunk/Lib/sqlite3/test/regression.py
> > python/trunk/Lib/sqlite3/test/types.py
> > python/trunk/Lib/sqlite3/test/userfunctions.py
> > python/trunk/Modules/_sqlite/connection.c
> > python/trunk/Modules/_sqlite/cursor.c
> > python/trunk/Modules/_sqlite/module.c
> > python/trunk/Modules/_sqlite/module.h
> > Log:
> > Merged changes from external pysqlite 2.3.0 release. Documentation updates will
> > follow in a few hours at the latest. Then we should be ready for beta1.
>> Please note that many (all?) non-Windows buildbots are failing
> test_sqlite now, and this one is even pumping out complaints from the
> system malloc()/free():
>> http://www.python.org/dev/buildbot/all/g4%20osx.4%20trunk/builds/1009/step-test/0
>> That's not really what we want to see in beta1 :-)

Conditional jump or move depends on uninitialised value(s)
 at 0x62D5998: sqlite3VdbeMemRelease (vdbemem.c:196)
 by 0x62D5CDB: sqlite3VdbeMemSetStr (vdbemem.c:383)
 by 0x62D28FC: sqlite3_result_error (vdbeapi.c:97)
 by 0x618CBA3: _step_callback (connection.c:561)
 by 0x62CE083: sqlite3VdbeExec (vdbe.c:4393)
 by 0x62D2B0C: sqlite3_step (vdbeapi.c:211)
 by 0x6192DAD: _sqlite_step_with_busyhandler (util.c:33)
 by 0x618FD97: _query_execute (cursor.c:610)
 by 0x61904DD: cursor_execute (cursor.c:721)
 by 0x4F8FCD: PyCFunction_Call (methodobject.c:73)
Conditional jump or move depends on uninitialised value(s)
 at 0x62D5998: sqlite3VdbeMemRelease (vdbemem.c:196)
 by 0x62D5CDB: sqlite3VdbeMemSetStr (vdbemem.c:383)
 by 0x62D28FC: sqlite3_result_error (vdbeapi.c:97)
 by 0x618CC74: _step_callback (connection.c:585)
 by 0x62CE083: sqlite3VdbeExec (vdbe.c:4393)
 by 0x62D2B0C: sqlite3_step (vdbeapi.c:211)
 by 0x6192DAD: _sqlite_step_with_busyhandler (util.c:33)
 by 0x618FD97: _query_execute (cursor.c:610)
 by 0x61904DD: cursor_execute (cursor.c:721)
 by 0x4F8FCD: PyCFunction_Call (methodobject.c:73)
53 bytes in 1 blocks are definitely lost in loss record 13 of 286
 at 0x4A19B7E: malloc (vg_replace_malloc.c:149)
 by 0x62CC36A: sqlite3MallocRaw (util.c:276)
 by 0x62D582B: sqlite3VdbeMemMakeWriteable (vdbemem.c:99)
 by 0x62D5D6A: sqlite3VdbeMemSetStr (vdbemem.c:433)
 by 0x62D28FC: sqlite3_result_error (vdbeapi.c:97)
 by 0x618CC74: _step_callback (connection.c:585)
 by 0x62CE083: sqlite3VdbeExec (vdbe.c:4393)
 by 0x62D2B0C: sqlite3_step (vdbeapi.c:211)
 by 0x6192DAD: _sqlite_step_with_busyhandler (util.c:33)
 by 0x618FD97: _query_execute (cursor.c:610)
 by 0x61904DD: cursor_execute (cursor.c:721)
 by 0x4F8FCD: PyCFunction_Call (methodobject.c:73)
57 bytes in 1 blocks are definitely lost in loss record 14 of 286
 at 0x4A19B7E: malloc (vg_replace_malloc.c:149)
 by 0x62CC36A: sqlite3MallocRaw (util.c:276)
 by 0x62D582B: sqlite3VdbeMemMakeWriteable (vdbemem.c:99)
 by 0x62D5D6A: sqlite3VdbeMemSetStr (vdbemem.c:433)
 by 0x62D28FC: sqlite3_result_error (vdbeapi.c:97)
 by 0x618CBA3: _step_callback (connection.c:561)
 by 0x62CE083: sqlite3VdbeExec (vdbe.c:4393)
 by 0x62D2B0C: sqlite3_step (vdbeapi.c:211)
 by 0x6192DAD: _sqlite_step_with_busyhandler (util.c:33)
 by 0x618FD97: _query_execute (cursor.c:610)
 by 0x61904DD: cursor_execute (cursor.c:721)
 by 0x4F8FCD: PyCFunction_Call (methodobject.c:73)