Hi Philippe, Thank you for your reply.
1) I am using valgrind-3.17.0 on a Ubuntu 21.10 box (sorry I had incorrectly mentioned Ubuntu 20.04 in my original report). Not sure if this is the latest release or not. 2) I did not try it with --tool=none. It takes some time of testing to happen even with memcheck so not sure a none tool would help. 3) Yes this is the first error that I encounter. And I had tried the approach that you suggest with --vgdb-error=1 and did attach to the process through gdb at exactly the point when the error is issued. But did not know what more to do then. The application stack trace looks good just like I would expect. 4) I am not sure how to make use of the debug switches in further analyzing this. I have found a workaround for my issue and that is to remove a 1Mb allocation in the stack and move it to the heap. For reasons not yet known, that made the error disappear. So I have decided to move on for now. To me, the symptoms I have seen so far make it seem like a valgrind issue and not an application issue. If there is anything that you or other valgrind experts would like to know from the failing case, I can try work with you. Thanks again. Narayanan. _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
