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
: 'valgrind-users@lists.sourceforge.net'; Yanai, Omer (oya...@nds.com)
Subject: RE: [Valgrind-users] Valgrind shows Invalid write os size 4 for
memory allocated for the stack
Hello,
Attaching the reproducer - please compile it with gcc -g tmpthread.c -o
tmpthread -lpthread And then run: tmpthread
On Wed, 2013-07-24 at 14:05 +, 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
@lists.sourceforge.net
Subject: Re: [Valgrind-users] Valgrind shows Invalid write os size 4 for
memory allocated for the stack
On Mon, 2013-06-10 at 01:23 -0700, mnaret wrote:
Hello,
Recently I'm getting lot's of invalid read/invalid write valgrind
errors which point out at memory allocated for the stack. However
-
From: Philippe Waroquiers [mailto:philippe.waroqui...@skynet.be]
Sent: Wednesday, June 12, 2013 10:44 PM
To: Masha Naret (mnaret)
Cc: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Valgrind shows Invalid write os size 4 for
memory allocated for the stack
On Mon, 2013-06-10
On Mon, 2013-06-10 at 01:23 -0700, mnaret wrote:
Hello,
Recently I'm getting lot's of invalid read/invalid write valgrind errors
which point out at memory allocated for the stack. However the code doesn't
crush and finish running successfully.
I'm trying to understand where the error comes
Hello,
Recently I'm getting lot's of invalid read/invalid write valgrind errors
which point out at memory allocated for the stack. However the code doesn't
crush and finish running successfully.
I'm trying to understand where the error comes from - and will be grateful
fo any help wih this issue.
(gdb) monitor v.info last_error
==10259== Invalid write of size 4
==10259==at 0x28686C: vsnprintf (in /lib/libc-2.12.so)
==10259== Address 0x4b43040 is 45,120 bytes inside a block of size 65,536
alloc'd
==10259==at 0x4005DB9: memalign (vg_replace_malloc.c:727)
==10259==by
