[snip]

>Yet another "me too". I'm seeing it on several 3/60's here. I did
>notice the ldd corrupt output as well. At one point the problem seemed to
>persist over a reboot, but thats probably just a red herring.
>
>Jon


An i386 "me too", as one notices in the output below....


anduin% ldd /usr/X11R6/bin/xterm 
/usr/X11R6/bin/xterm:
        -lXaw.6 => /usr/X11R6/lib/libXaw.so.6.0 (0x10037000)
        -lXmu.6 => /usr/X11R6/lib/libXmu.so.6.0 (0x1006d000)
        -l:%s/%%N%%C:%s/%%L/%%N:%s/%%l/%%N:%s/%%N:%s/%%N.6 => /usr/X11R6/lib/libXt.so.6.0 (0x1007d000)
        -l/%%N%%C:%s/%%L/%%N:%s/%%l/%%N:%s/%%N:%s/%%N.6 => /usr/X11R6/lib/libX11.so.6.0 (0x100be000)
        -lSM.6 => /usr/X11R6/lib/libSM.so.6.0 (0x10138000)
        -lICE.6 => /usr/X11R6/lib/libICE.so.6.0 (0x10140000)
        -lXext.6 => /usr/X11R6/lib/libXext.so.6.0 (0x10152000)
        -lgnumalloc.0 => /usr/lib/libgnumalloc.so.0.0 (0x1015a000)
        -ltermcap.0 => /usr/lib/libtermcap.so.0.0 (0x1015e000)
        -lc.12 => /usr/lib/libc.so.12.3 (0x10160000)

A quick check would seem to indicate that several of the X binaries
exhibit this behavior.  With a couple of exceptions, it would seem
that every instance libXt and libX11 show up as corrupt, each unique
in what garbage gets displayed [nothing else appears to as corrupt].

The binaries appear to run correctly, in any case.


Brad Spencer - brad@anduin.eldar.org   http://anduin.eldar.org