15 Apr
2016
15 Apr
'16
2:50 p.m.
On 04/15/2016 07:22 AM, Richard W.M. Jones wrote:
BTW this causes valgrind to fail in a particularly strange way. I filed a bug upstream with a minimal reproducer. Do you have any ideas?
Weird - it looks like valgrind is somehow calling lseek on stdin, wiping out the buffer that it previously read. Since it doesn't happen when the program is run standalone, I'm thinking this is a valgrind bug. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org