Previously, the handle debuginfod_so created by dlopen was not closed
in all cases, leading to a potential resource leak. This commit adds an
additional dlclose call to ensure that the handle is always properly
released, whether the symbols are successfully loaded or not.
Found by RASU JSC.
Si
Hi -
On Fri, Nov 01, 2024 at 07:37:03PM +0300, Anton Moryakov wrote:
> Previously, the handle debuginfod_so created by dlopen was not closed
> in all cases, leading to a potential resource leak. This commit adds an
> additional dlclose call to ensure that the handle is always properly
> release
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
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
Ping
Thanks,
Ying
在 2024/10/12 17:40, Ying Huang 写道:
> Ping
>
>
> Thanks,
>
> Ying
>
>
> 在 2024/9/27 17:52, Ying Huang 写道:
>> Ping
>>
>>
>> Thanks,
>>
>> Ying
>>
>>
>> 在 2024/9/14 17:45, Ying Huang 写道:
>>> Ping
>>>
>>>
>>> Thanks,
>>>
>>> Ying
>>>
>>>
>>> 在 2024/8/30 17:04, Ying Huang 写道: