Re: [Valgrind-users] valgrind-2.1.0 (unstable release) is available

[Jeremy F. <je...@go...>]

On Mon, 2003-12-15 at 06:21, Crispin Flowerday wrote:
> Apart from the inherit failure (which looks like a known failure??),
> these are all of the form (obviously with different system calls)
> 
> ***************
> *** 2 ****
> !    at 0x........: __ioctl (in /...libc...)
> --- 2 ----
> !    at 0x........: ioctl (in /...libc...)

I just checked in a fix to canonicalize these aliased symbols so that
the plain form "ioctl" is preferred over "__ioctl", "__libc_ioctl", etc,
even though the general policy is to prefer the longer name.

I hope this will make error reports a bit more consistent over different
versions of glibc.

	J