Very Computer

I've got a program (GUI for Arkeia backup software) that has started
segfaulting for normal users but not for root.  This only started
happening after I recently upgraded WindowMaker from 0.20 to 0.50, but
I'm at a loss to understand what the connection is, if any.

The system is a Red Hat 5.1 installation.

Checking ldd while root gives:

#ldd /usr/knox/bin/arkx
        libX11.so.6 => /usr/i486-linux-libc5/lib/libX11.so.6 (0x4000d000)
        libm.so.5 => /usr/i486-linux-libc5/lib/libm.so.5 (0x4009f000)
        libc.so.5 => /usr/i486-linux-libc5/lib/libc.so.5 (0x400a7000)

Checking ldd for Joe user gives:

$ldd /usr/knox/bin/arkx
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4000d000)
        libm.so.5 => /usr/i486-linux-libc5/lib/libm.so.5 (0x400a4000)
        libc.so.5 => /usr/i486-linux-libc5/lib/libc.so.5 (0x400ac000)
        libc.so.6 => /lib/libc.so.6 (0x40175000)
        ld-linux.so.2 => /lib/ld-linux.so.2 (0x4025a000)

OK, so it looks like there's a problem with using libc.so.6 in
addition to libc.so.5.  But wait, on another machine where the same
program (installed as a binary) runs fine for both root and users, ldd
shows:

$ ldd /usr/knox/bin/arkx
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40003000)
        libm.so.5 => not found
        libc.so.5 => not found
        libc.so.6 => /lib/libc.so.6 (0x4009a000)
        /lib/ld-linux.so.1 => /lib/ld-linux.so.2 (0x00000000)

So on this machine, libc6 works OK.

Can anyone give me some pointers as to what might be happening here,
or some things to check?

Thanks,
--
Dave Guertin