|
From: Jeffrey W. <nol...@gm...> - 2015-10-02 16:33:27
|
I'm catching a finding on a call to localtime() on OS X 10.8. I'm using Valgrind 3.11.0, and I compiled with -O1. I think Apple dynamically allocates the tm struct rather than making it statically allocated. I see others have encountered the same issue on OS X (cf., http://stackoverflow.com/q/10105181 and http://stackoverflow.com/q/15613511). Please consider ignoring leak findings for localtime() under OS X. |
|
From: Rhys K. <rhy...@gm...> - 2015-10-15 03:37:13
|
Hello Jeffrey, Thank you for the report. I'll take a look into it. Regards, Rhys On 3 October 2015 at 02:33, Jeffrey Walton <nol...@gm...> wrote: > I'm catching a finding on a call to localtime() on OS X 10.8. I'm > using Valgrind 3.11.0, and I compiled with -O1. > > I think Apple dynamically allocates the tm struct rather than making > it statically allocated. I see others have encountered the same issue > on OS X (cf., http://stackoverflow.com/q/10105181 and > http://stackoverflow.com/q/15613511). > > Please consider ignoring leak findings for localtime() under OS X. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |