three bugs of memory leak
Brought to you by:
alexis_wilke,
dooglio2
Menu
▾
▴
#2 three bugs of memory leak
- odbcpp::record's two members： f_bind_by_name and f_bind_by_col, the default destructor of them cann't release the allocated memory of key mapped value(it is a pointer).
- odbcpp::dynamic_record: the same of above happens to the class.
- odbcpp::dynamic_record::bind_impl, the statement "info->f_data.reset(new buffer_char_t(info->f_size));", cause memory leak.
I have fixed the source code, and programme that uses the fixed odbcpp runs well, you can use valgrind to check the memory leak, it will print some useful information. contact me by: zhongwl@suntang.com or zhongwl@gmail.com.
odbcpp::record::bind_impl, the statement "info->f_data.reset(new buffer_char_t(info->f_size));", maybe the same as what happens to dynamic_record, may cause memory leak. bug1 and bug2 is obvious, the other bugs is also notified by valgrind, I think you can use odbcpp::smartptr to manage the bind_info_t *.