Re: [Valgrind-users] Malloc/free in different threads
Thank you! Found the bug in my code! From: Philippe Waroquiers Sent: Friday, December 18, 2020 10:04 AM To: Saurabh T ; Valgrind Subject: Re: [Valgrind-users] Malloc/free in different threads Hello, No, valgrind/memcheck leak search is not impacted by the fact that one thread allocates some memory and that the release/free is done by another thread. That should not lead to a definite leak. So, if Valgrind tells that there are definite leaks, that is likely real leaks to be investigated. Philippe On Fri, 2020-12-18 at 14:53 +, Saurabh T wrote: > Sorry I forgot to say the false positives are for memory leaks ("definitely > lost"). > > > From: Saurabh T > Sent: Friday, December 18, 2020 9:44 AM > To: Valgrind > Subject: [Valgrind-users] Malloc/free in different threads > > Hi, I believe I am seeing lots of false positives in valgrind if I call > free() on a different thread from the one that called malloc() - > the pointers are exchanged between threads safely in between. Is this a known > issue, or am I doing something wrong? Thank you. > > ___ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
Re: [Valgrind-users] Malloc/free in different threads
Hello, No, valgrind/memcheck leak search is not impacted by the fact that one thread allocates some memory and that the release/free is done by another thread. That should not lead to a definite leak. So, if Valgrind tells that there are definite leaks, that is likely real leaks to be investigated. Philippe On Fri, 2020-12-18 at 14:53 +, Saurabh T wrote: > Sorry I forgot to say the false positives are for memory leaks ("definitely > lost"). > > > From: Saurabh T > Sent: Friday, December 18, 2020 9:44 AM > To: Valgrind > Subject: [Valgrind-users] Malloc/free in different threads > > Hi, I believe I am seeing lots of false positives in valgrind if I call > free() on a different thread from the one that called malloc() - > the pointers are exchanged between threads safely in between. Is this a known > issue, or am I doing something wrong? Thank you. > > ___ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
Re: [Valgrind-users] Malloc/free in different threads
Sorry I forgot to say the false positives are for memory leaks ("definitely lost"). From: Saurabh T Sent: Friday, December 18, 2020 9:44 AM To: Valgrind Subject: [Valgrind-users] Malloc/free in different threads Hi, I believe I am seeing lots of false positives in valgrind if I call free() on a different thread from the one that called malloc() - the pointers are exchanged between threads safely in between. Is this a known issue, or am I doing something wrong? Thank you. ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
[Valgrind-users] Malloc/free in different threads
Hi, I believe I am seeing lots of false positives in valgrind if I call free() on a different thread from the one that called malloc() - the pointers are exchanged between threads safely in between. Is this a known issue, or am I doing something wrong? Thank you. ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users