On 01/05/2018 01:26 PM, Stephan Bergmann wrote:
On 01/05/2018 12:41 PM, Mark Wielaard wrote:
On Thu, Jan 04, 2018 at 09:36:27PM -0800, John Reiser wrote:
2) The explicit write by the stack probe can mask a memcheck(valgrind)
violation, at least until memcheck groks the probe.
That should not be true. The probe is done after the stack pointer is
lowered, so memcheck/valgrind knows that memory is used.
But if, as claimed, the probe is done by writing (a fixed value) instead
of reading, couldn't that hide later memcheck reports about use of
uninitialized memory?
On x86, probing uses an OR with 0, and that does not change the
initialization status of the memory as far as valgrind is concerned.
Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
