Re: [gtk-list] Re: sigsegv on gtk_signal_connect

[Tomi Ollila <Tomi Ollila tfi net>]

Thu Jul 9 09:43:03 +0200 1998 Didimo Emilio Grimaldo Tunon <emilio_tunon@nl.compuware.com> wrote:
>   I am not sure whether it is your problem but I somethings get that
>   signal when I accidentally run my 1.0.4 executable without the wrapper
>   script, as a result it runs with the 0.99 library and then breaks.
>   I have 0.99 in the normal path/location and 1.0.4 on /opt (RH). My
>   wrapper script sets LD_LIBRARY_PATH to first point to the 1.0.4
>   libs (/opt/lib) and it runs fine.

What platform are you using. I've heard (not tested, though), that some
platforms considers it as a security feature that paths given in
/etc/ld.so.conf (actually ls.so.cache) is searched first and then paths in 
LD_LIBRARY_PATH.

Well, I proved myself wrong testing this on Linux (glibc) platform
(but maybe on some other platform...):

lame ~ % ldd =gimp         
        libgtk.so.1 => /usr/lib/libgtk.so.1 (0x40004000)
        libgdk.so.1 => /usr/lib/libgdk.so.1 (0x400a4000)
        libglib.so.1 => /usr/lib/libglib.so.1 (0x400c3000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400d0000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400dd000)
        libm.so.6 => /lib/libm.so.6 (0x40174000)
        libc.so.6 => /lib/libc.so.6 (0x4018d000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)
lame ~ % touch /tmp/libgtk.so.1
lame ~ % export LD_LIBRARY_PATH=/tmp
lame ~ % ldd =gimp
/usr/bin/gimp: error in loading shared libraries
libgtk.so.1: invalid ELF header
zsh: exit 127   ldd /usr/bin/gimp
lame ~ % gimp
gimp: error in loading shared libraries
libgtk.so.1: invalid ELF header
zsh: exit 127   gimp
lame ~ % unset LD_LIBRARY_PATH     

> 
> -- 
> D. Emilio Grimaldo Tunon       Compuware Europe B.V. (Uniface Lab)

Tomi