Re: [PATCH] Fix potential handle leak by ensuring dlclose is always called on debuginfod_so

Hi - > first report > HANDLE_LEAK.EX The handle 'debuginfod_so' is created at > debuginfod-client.c:104 by calling function 'dlopen' and lost at > debuginfod-client.c:129. > second report > HANDLE_LEAK.EX The handle 'debuginfod_so' is created at > debuginfod-client.c:107 by calling function 'dl

[PATCH] Fix potential handle leak by ensuring dlclose is always called on debuginfod_so

first report HANDLE_LEAK.EX The handle 'debuginfod_so' is created at debuginfod-client.c:104 by calling function 'dlopen' and lost at debuginfod-client.c:129. second report HANDLE_LEAK.EX The handle 'debuginfod_so' is created at debuginfod-client.c:107 by calling function 'dlopen' and lost at de