valgrind suppressions: ignore XInitThreads leaks
As we load that symbol dynamically, valgrind gets confused when it leaks and reports the leak against an unrelated library and an unknown (??) symbol. To address that, put the loading and calling of that symbol in a separate function, and ignore any malloc leak happening in that function.
Showing with 25 additions and 5 deletions