> I dont understand the change in behaviour due to valgrind. Is this a
> known issue or a bug?
This is a bug in the strspn replacement, used a.o. by memcheck,
helgrind, ...
I fixed it in commit c1eace647ca4f670ef9bec0d0fe72cdd25a96394
Now, your small test case works similarly with or without valg
Hi all,
I'm having an issue running a application under valgrind.
The application runs fine without it, but some code has a different
behaviour with valgrind.
I've managed to track and isolate the issue to the following piece (full
example is attached as test.c) :
//work4 = 0x e2 e3 d9
