Re: [Valgrind-users] Valgrind shows "Invalid write os size 4" for memory allocated for the stack

[Philippe W. <phi...@sk...>]

On Wed, 2013-07-24 at 22:08 +0200, Philippe Waroquiers wrote:

> At this moment, the hypothesis is that if the stack memory is
> managed by the user, then when the thread terminates, the stack memory
> is not marked by memcheck as addressible again.
> I need to investigate more in depth to confirm this hypothesis.
Investigations have confirmed the hyposthesis and have lead to
https://bugs.kde.org/show_bug.cgi?id=323020
which summarises/collects several strange aspects of thread stack
handling.

At this point, the only possible fix I see is to add a valgrind client
request in your code to mark the released stack as accessible.

No clear way how this can be done automatically by valgrind, without
introducing the risk of more false positive and/or false negative.

Philippe