On 3/9/18 5:45 PM, Bart Van Assche wrote: > The Valgrind memory checker can only detect uninitialized reads and > out-of-bounds writes if it knows about the dynamic memory allocation > calls performed by an application. There are two ways to inform > Valgrind about the sfree(), smalloc() and scalloc() calls: > * Call the glibc equivalents if running on Valgrind. > * By using the Valgrind memory pool client requests. See also > http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools. > > Since the former approach is the easiest to implement, follow that > approach. smalloc() is shared memory backed, it's not process private. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
