On Mon, 14 Oct 2024 at 13:35, Giuseppe D'Angelo via Std-Proposals <
std-proposals_at_[hidden]> wrote:

> On 14/10/2024 12:22, Frederick Virchanza Gotham via Std-Proposals wrote:
> >
> > But what if the allocation takes place inside a proprietary shared
> > library? Here's a patch I wrote for libpango to clean up the output
> > from valgrind:
>
> Or you write a suppression file.
>

Or use the existing one that the project already provides for exactly this
purpose:
https://gitlab.gnome.org/GNOME/pango/-/blob/main/pango.supp



>
> Or you contribute a feature to valgrind so that you can use some of its
> APIs to mark memory that you're going to deliberately leak and the tool
> doesn't complain about it (... if such an API doesn't exist already in
> memcheck.h).
>
>
> For the Nth time, please write *concrete* proposals, not wishlists.
>
> Thank you,
> --
> Giuseppe D'Angelo
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>