[vlc-devel] [PATCH] libvlc: help debug object references remaining in debug builds

Rémi Denis-Courmont remi at remlab.net
Fri Aug 17 13:29:20 CEST 2018

The debugger is not always attached but likewise the standard error. So this does not solve the problem.

We have far superior mechanisms to track leaks already. Adding ad-hoc mechanisms seems like a complete waste of time and code complexity.

Le 17 août 2018 12:33:44 GMT+03:00, Thomas Guillem <thomas at gllm.fr> a écrit :
>Maybe, we should bring this patch back ?
>The debugger is not always attached, and sometimes you can't reproduce
>a leak. 
>I often use this patch to get the actual leak...
>On Fri, Aug 17, 2018, at 10:59, Jean-Baptiste Kempf wrote:
>> Hello,
>> On Fri, 17 Aug 2018, at 08:41, Steve Lhomme wrote:
>> > No, before we could follow internals->first in the debugger. Now
>> > [...]
>> > internals->siblings which just had garbage in it. I tried 
>> > vlc_list_foreach(), vlc_list_first_entry_or_null() no luck.
>> I would argue that we need to be able to have the list of leaked item
>> easily, and not only with a debugger, notably for user reports;
>> but the vlc_list is fine and a good idea.
>> -- 
>> Jean-Baptiste Kempf -  President
>> +33 672 704 734
>> _______________________________________________
>> vlc-devel mailing list
>> To unsubscribe or modify your subscription options:
>> https://mailman.videolan.org/listinfo/vlc-devel
>vlc-devel mailing list
>To unsubscribe or modify your subscription options:

Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20180817/cf83568a/attachment.html>

More information about the vlc-devel mailing list