Bug 20738 - Valgrind обнаруживает внутренние проблемы в SQLite
: Valgrind обнаруживает внутренние проблемы в SQLite
Status: CLOSED NOTABUG
: Sisyphus
(All bugs in Sisyphus/sqlite3)
: unstable
: all Linux
: P3 major
Assigned To:
:
:
:
:
:
  Show dependency tree
 
Reported: 2009-07-10 12:15 by
Modified: 2009-10-01 21:40 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-07-10 12:15:49
Версия библиотеки: sqlite3-3.6.16-alt1
Valgrind сообщает следующее:
==5608== Thread 26:
==5608== Syscall param write(buf) points to uninitialised byte(s)
==5608==    at 0x4376C01: write (in /lib/libc-2.10.1.so)         
==5608==    by 0x6C3DDA7: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C3C13C: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C418F7: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C43712: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C17F65: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C6B76E: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C6BF1B: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C600AD: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C683EA: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608==    by 0x6C6859E: sqlite3_step (in /usr/lib/libsqlite3.so.0.8.6)
==5608==    by 0x6C3709F: sqlite3_exec (in /usr/lib/libsqlite3.so.0.8.6)
==5608==  Address 0x174a9d6e is 134 bytes inside a block of size 1,168 alloc'd
==5608==    at 0x402513D: malloc (vg_replace_malloc.c:207)                    
==5608==    by 0x6C3B6DB: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C3AAC3: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C3AB85: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C482B6: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C483B4: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C48C01: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C479F6: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C42950: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C15C4B: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C1A70B: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C1B764: (within /usr/lib/libsqlite3.so.0.8.6)  
==5608== Syscall param write(buf) points to uninitialised byte(s)             
==5608==    at 0x4376C01: write (in /lib/libc-2.10.1.so)                      
==5608==    by 0x6C3DDA7: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C3C13C: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C3EE2A: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C43027: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C43387: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C1B395: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C1D436: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C64E54: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C683EA: (within /usr/lib/libsqlite3.so.0.8.6)               
==5608==    by 0x6C6859E: sqlite3_step (in /usr/lib/libsqlite3.so.0.8.6)      
==5608==    by 0x6C3709F: sqlite3_exec (in /usr/lib/libsqlite3.so.0.8.6)      
==5608==  Address 0x1c24328c is on thread 26's stack

Вероятно там действительно есть скрытая проблема и не мешало-бы уведомить Main
Stream.
------- Comment #1 From 2009-09-25 22:20:03 -------
айаяй