i386 memory fence incompatible with valgrind
matthias at urlichs.de
Tue Jan 10 20:03:49 CET 2017
valgrind does this on i386:
#define ECB_MEMORY_FENCE __asm__ __volatile__ ("lock; orb
$0, -1(%%esp)" : : : "memory")
This code triggers a warning whenever it is executed under valgrind:
whatever is below the stack pointer is undefined memory by definition.
Not a good idea, as this causes legitimate warnings to get lost in the
Please access a legitimate memory location instead.
-- Matthias Urlichs
More information about the libev