|
From: Dennis L. <pla...@in...> - 2005-08-01 21:04:41
|
At 22:43 01.08.2005, Dirk Mueller wrote: >On Monday 01 August 2005 14:45, Dennis Lubert wrote: > > > Looks like the SIOCGIFNAME bug mentioned a while ago on the list (and fixed > > in 3.x then) isnt yet fixed in this... > >you know which change in particular is responsible for this? there is no hit >for SIOCGIFNAME anywhere inside the valgrind-2.4 tree. coregrind/vg_syscalls.c l. 3044 ff. There is some integer parameter to the ioctl which is the index of the interface, which is misinterpreted by valgrind as an address thus causing a false "inaccesible memory passed to ioctl" error by valgrind. (It was on the list just a while ago and fixed in 3.x tree) greets Dennis Carpe quod tibi datum est |