On 5/1/22 10:16, Bjarni Ingi Gislason wrote:
I checked what of the about 30 options, I use for compiling "groff", could cause the only warning (leak) about "vasnprintf.c" and it was the "-flto".
Ah, the "-flto" suggests that the problem isn't in vasnprintf per se; it's in groff, which isn't freeing storage allocated by vasnprintf.
Possibly it's a real memory leak, but possibly it's not really a problem at all. It's OK - indeed, a win - to not free storage if you're about to exit anyway.
The compilation of "groff" then got finished with a lot of warnings (149) about its code.
It's up to you as to whether to investigate these warnings more carefully. Please check to see whether they actually make sense before reporting, due to the high number of false positives in this area.
