-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try running:
which ion3 ldd `which ion3` Make sure you don't have a version of a library in both /usr/local/lib and /usr/lib, e.g.. If ldd reports you are using an older version in /usr/local/lib, you might want to remove it. I was getting a similar message recently with another program and that was the solution. - --Kevin On Wed, Oct 12, 2005 at 02:52:47PM -0400, Geoffrey Alan Washburn wrote: > Tuomo Valkonen wrote: > >On 2005-10-12, Geoffrey Alan Washburn <[EMAIL PROTECTED]> wrote: > > > >>So it looks like it is something in glibc on the system I am using. > >>However, with some investigation I was unable to determine which version > >>of glibc introduced this "feature" or whether there is any way to turn > >>it off. > > > > > >Hmm.. I indeed have such strings too in libc, so those could be its > >diagnostics.. but why is it printing ***glibc detected*** or whatever > >it was? > > > > > >>Regardless, has anyone tried running valgrind (or equivalent) on ion3? > > > > > >Yeah, only complains of dlopen and xlib... > > > > Hmmm. I'm stumped as to what to do next. I'm assuming no one else > has seen behavior like this then? I guess I'll just have to stick with > ion2 and try examining more closely what is happening with gdb when I have > more time. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDTv/6A2vFsoV0MMQRAnidAJ9MrGtaJXwcIvvTy2OUwBf+inXRMgCcDdkL 23xra+pFyH2u1ysdHoEJf+k= =xIaT -----END PGP SIGNATURE-----
