On 2022-05-11 16:01, Kim Barrett wrote:
Globally disabling use-after-free warnings for this package seems really questionable. If these are problems in the code, just suppressing the warning and leaving the problems to bite us seems like a bad idea. And the problems ought to be reported upstream to the HarfBuzz folks.
I agree that an upstream report would be nice, but it has been a long-standing policy of not changing 3rd party code to fix warnings, but instead suppress them. (Most of the time we compile with a much larger set of warnings enabled than the upstream's own build does, so we trigger warnings they never even see.)
/Magnus
