Yes, that suppresses chkstk's accesses, but also suppresses actual
invalid uses of stack-relative pointers.
Jefferson
On 11/18/2019 8:36 AM, Julian Seward wrote:
Did you look into using the following option?
--ignore-range-below-sp=<number>-<number> do not report errors for
accesses at the given offsets
below SP
J
On 18/11/2019 09:02, Jefferson Carpenter wrote:
I'm debugging a mingw-compiled exe running under Wine, and I'm getting
some invalid reads in chkstk. Assuming I don't want to "skip past"
them but detect and suppress them, the most natural thing to do would
be to create and use a suppressions file.
However, the code that calls into chkstk is loaded outside of the
normal "dlopen" code path, and neither Valgrind nor GDB loads symbols
for it before it is jumped into. With GDB I can use "add-symbol-file"
to state where to find the symbols for it. Does Valgrind have a
similar option?
Thanks,
Jefferson
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
