> > Compile Jade with "-g" and see where in the coredump the signal 11 is > > occuring.? What does ``ldd jade'' show?? You might be mixing shared libs, > > that doesn't work for C++.? Could also be an exceptions problem.? Try > > compiling with -fnoexpcetions. > > [asmo...@daemon] (163) $ ldd /usr/local/bin/jade > /usr/local/bin/jade: > ??????? libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b6000) > ??????? libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282ac000) > ??????? libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282ef000) > ??????? libsp.so.1 => /usr/local/lib/libsp.so.1 (0x282f7000) > ??????? libintl.so.1 => /usr/local/lib/libintl.so.1 (0x284ce000) > ??????? libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284d2000) > ??????? libm.so.2 => /usr/lib/libm.so.2 (0x2850d000) > ??????? libc.so.3 => /usr/lib/libc.so.3 (0x28527000) > > I know for certain that libintl is gcc. > > Will go and do recompilations of all stuff this weekend *sigh*? ;) > ?
In my case (it seems all libs compiled under egcs - exactly when jade compiled): /usr/local/bin/jade: ??????? libstyle.so.1 => /usr/local/lib/libstyle.so.1 (0x280b9000) ??????? libspgrove.so.1 => /usr/local/lib/libspgrove.so.1 (0x282b6000) ??????? libgrove.so.1 => /usr/local/lib/libgrove.so.1 (0x282f9000) ??????? libsp.so.1 => /usr/local/lib/libsp.so.1 (0x28301000) ??????? libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x284e4000) ??????? libm.so.2 => /usr/lib/libm.so.2 (0x28521000) ??????? libc.so.3 => /usr/lib/libc.so.3 (0x2853c000) ? To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
