Hi, It would be very helpful, if you can provide us some info on the below issues (Memory leak & Invalid write errors, found from valgrind tool on libdbi drivers library usage).
Executed some Select & Update queries. Don't know if these issue got fixed in the latest libdbi drivers library- Sorry for the long mail. Attached below the callflows, for to give more detailed info. Thanks, Kishore Invalid read/write error - 1. ==22067== Invalid read of size 1 ==22067== at 0x40367D3: get_field_type (in /usr/local/lib/dbd/libdbdsqlite3.so) ==22067== by 0x4036C7B: find_result_field_types (in /usr/local/lib/dbd/libdbdsqlite3.so) ==22067== by 0x40372B3: dbd_query (in /usr/local/lib/dbd/libdbdsqlite3.so) ==22067== by 0x40803FA: dbi_conn_query (in /usr/lib/libdbi.so.0.0.5) ==22067== by 0x40414BF: start_thread (in /lib/i686/cmov/libpthread-2.7.so) ==22067== by 0x41686DD: clone (in /lib/i686/cmov/libc-2.7.so) ==22067== Address 0x45786b4 is 0 bytes after a block of size 1,740 alloc'd 2. ==22067== Invalid write of size 1 ==22067== at 0x40367D8: get_field_type (in /usr/local/lib/dbd/libdbdsqlite3.so) ==22067== by 0x4036C7B: find_result_field_types (in /usr/local/lib/dbd/libdbdsqlite3.so) ==22067== by 0x40372B3: dbd_query (in /usr/local/lib/dbd/libdbdsqlite3.so) ==22067== by 0x40803FA: dbi_conn_query (in /usr/lib/libdbi.so.0.0.5) ==22067== by 0x406858E: ExecuteSelectQuery (Ran select query here) ==22067== by 0x41686DD: clone (in /lib/i686/cmov/libc-2.7.so) ==22067== Address 0x4578d3c is not stack'd, malloc'd or (recently) free'd ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
