Re: dlopen segv in ppc libc6 pkg
On Thu, 2002-09-19 at 16:42, Daniel Jacobowitz wrote:
> Well, that's not the right behavior probably. We'd need more
> information.
agreed :)
> But it looks to me from the GDB trace as if you're dlopening a library
> which is linked to libpthread, and your main application is not. I can
> assure you that that isn't going to work properly. If you want to
> support threaded plugins the app must be threaded.
How about the other way around?
ldd on the executable:
lqt_mjpeg.so => not found
libquicktime.so.0 => not found [these are in a sep build tree for now...]
libquicktime1394.so.0 => not found
libtiff.so.3 => /usr/lib/libtiff.so.3 (0x0ff94000)
libmpeg3.so.1 => /usr/lib/libmpeg3.so.1 (0x0ff12000)
libsndfile.so.0 => /usr/lib/libsndfile.so.0 (0x0febd000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x0fe77000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x0fd69000)
libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x0fd42000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x0fc7a000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x0fb7f000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x0fb4d000)
libpthread.so.0 => /lib/libpthread.so.0 (0x0fb17000)
libpng.so.3 => /usr/lib/libpng.so.3 (0x0fac5000)
libz.so.1 => /usr/lib/libz.so.1 (0x0fa95000)
libdl.so.2 => /lib/libdl.so.2 (0x0fa72000)
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x0f9fb000)
libm.so.6 => /lib/libm.so.6 (0x0f964000)
libc.so.6 => /lib/libc.so.6 (0x0f809000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x0f7c6000)
librom1394.so.0 => /usr/lib/librom1394.so.0 (0x0f7a3000)
libavc1394.so.0 => /usr/lib/libavc1394.so.0 (0x0f780000)
libraw1394.so.5 => /usr/lib/libraw1394.so.5 (0x0f75d000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x0f739000)
/lib/ld.so.1 => /lib/ld.so.1 (0x30000000)
ldd deinterlace.plugin:
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x6ff60000)
libm.so.6 => /lib/libm.so.6 (0x6fec9000)
libc.so.6 => /lib/libc.so.6 (0x6fd6e000)
/lib/ld.so.1 => /lib/ld.so.1 (0x08000000)
which is the same libs linked to by another plugin which seems to load okay...
thanks for the help,
-m
Reply to: