Holger Hans Peter Freyther e1298b0b9d wireless-tools: Attempt to fix memory leak ... We would leak all the results for all the scans. At some point in time the kernel OOM would kick-in and kill the process. Enable building with -ggdb3 for debug symbols and remmeber the old list head so we can free it. ==32240== 756 bytes in 3 blocks are definitely lost in loss record 7 of 8 ==32240== at 0x40291CC: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==32240== by 0x804BCF5: iw_process_scanning_token (iwlib.c:3059) ==32240== by 0x804BCF5: iw_process_scan (iwlib.c:3255) ==32240== by 0x804BEAF: iw_scan (iwlib.c:3310) ==32240== by 0x8048FD8: scan_wifi (wifi2udp.c:72) ==32240== by 0x8048DB2: main (wifi2udp.c:143)		2014-11-18 09:37:53 +01:00
..
files	wireless-tools: Attempt to fix memory leak	2014-11-18 09:37:53 +01:00
wireless-tools_sysmocom.inc	wireless-tools: Attempt to fix memory leak	2014-11-18 09:37:53 +01:00