Red Hat Bugzilla – Bug 204920
memleak in db4
Last modified: 2013-07-02 19:17:28 EDT
Description of problem:
memleak on db->open
Version-Release number of selected component (if applicable):
Steps to Reproduce:
if (0 == db_create(&dbp, 0, DB_CXX_NO_EXCEPTIONS))
args 2 is DB_TXN *, 0 is valid from docs, but appears to cause
a mem leak
gcc db4test.c -lpthread -ldb
valgrind --leak-check=full ./a.out
==2837== 132 bytes in 1 blocks are definitely lost in loss record 1 of 1
==2837== at 0x40203C6: malloc (vg_replace_malloc.c:149)
==2837== by 0x638260E: __os_malloc (in /lib/libdb-4.3.so)
==2837== by 0x6382956: __os_calloc (in /lib/libdb-4.3.so)
==2837== by 0x6390FDB: __xa_get_txn (in /lib/libdb-4.3.so)
==2837== by 0x6391C5D: (within /lib/libdb-4.3.so)
==2837== by 0x80484A4: main (in /home/caolan/a.out)
related to 2nd arg of open
Are you sure that usage of DB_CXX_NO_EXCEPTIONS is intentional?
db_create supports only 0 or DB_XA_CREATE flags according to documentation,
luckily DB_CXX_EXCEPTIONS and DB_XA_CREATE are equivalent (==2).
The memleak was caused by broken SET_TXN macro in xa_db.c and occurs only when
db->open()ing with txnid == NULL.
Yeah, thanks, that looks dubious alright.
db4-4.3.29-7.fc5 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.