Opened 3 months ago

Last modified 3 months ago

#1567 new defect

valgrind for system tests

Reported by: bbell Owned by:
Priority: major Milestone: 10.0
Component: systemtest Version: development
Keywords: memleak, test, valgrind Cc: dmisev, vmerticariu, pbaumann
Complexity: Hard


In order to control memory leaks in Rasdaman, one should additionally pass system test queries in "test_select" with:

valgrind --leak-check=full directql 'query' -d DB_DIRECTORY

Ideally, one would parse the output of valgrind and use that data to determine whether or not a leak is excessive.

An initial threshold for when a leak is "too big" could be around 50kB; however, the size of the leak might be a linear function of the size of the stored data, so perhaps a few conditionals to determine pass/failure of queries would be of use here.

Change History (1)

comment:1 Changed 3 months ago by dmisev

  • Cc pbaumann added
Note: See TracTickets for help on using tickets.