On Wed, 2013-07-24 at 14:05 +0000, Masha Naret (mnaret) wrote: > Hello, > > Could anyone please comment the issue described below: > Valgrind shows "invalid write" for memory allocated on the stack while the > program runs normally. > I've attached a reproducer for this problem, Thanks for the reproducer, I started looking at this problem (limited time permitting :) some days ago. Stack management in valgrind is somewhat tricky (see e.g. revision r13467: fix 321960 pthread_create() then alloca() causing invalid stack write errors). However, r13647 does not fix your specific case. (you might however try the last SVN version on your full application).
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. Philippe ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
