#421 SelStatement::resolve() (SelStatement.cxx:385) leaks

V2.1 Beta
open
nobody
leak (188)
5
2009-01-30
2009-01-30
No

i have run ( sql / Aggregate / aggregate4.sql ) with valgrind tool as
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes csql -s
createt1t2.sql
valgrind --tool=memcheck --leak-check=yes --show-reachable=yes csql -s
aggregate4.sql
and found memory leakage as follows.

Error Summary :
==16220== 2,288 (192 direct, 2,096 indirect) bytes in 1 blocks are definitely lost in loss record 32 of 33
==16220== at 0x4005CCC: operator new(unsigned) (vg_replace_malloc.c:163)
==16220== by 0x405E549: SelStatement::resolve() (SelStatement.cxx:385)
==16220== by 0x4065C9B: SqlStatement::prepare(char*) (SqlStatement.cxx:67)
==16220== by 0x8049574: getInput(bool) (isql.cxx:304)
==16220== by 0x8049B11: main (isql.cxx:109)

Discussion

  • Nihar Ranjan paital

    refer test / sql / Aggregate / test004.ksh

     
  • Bijaya kumar Sahu

    This is fixed. There is no memory leak in aggregate function. This needs to be closed.

    File: SelStatement.cxx

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks