Date: Fri, 2 Feb 2007 16:40:18 -0500 From: "Gregory Nou" <gregory.nou@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Problem of segmentation fault with a lot of KDE programs Message-ID: <85c22ba00702021340k640fd0a2u61f4209c9ebd8315@mail.gmail.com> In-Reply-To: <85c22ba00702012048m710cee5dpf08db29298d407ca@mail.gmail.com> References: <85c22ba00702012048m710cee5dpf08db29298d407ca@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi again ! Replying to myself, as I made some progress, and would like to share them. I put the line : libpthread.so.2 libpthread.so.1 (which are /lib/libpthread.so.2 and /usr/local/lib/compat/libpthread.so.1) in /etc/libmap.conf and now, kdevelop, kdvi and amarok work... but with this tuning, Terminal and Mozilla are not working, and I suspect that it's the case for lot of other programs. Error is : /libexec/ld-elf.so.1: /usr/local/lib/compat/libpthread.so.1: Undefined symbol "__malloc_lock" So how could I make it work ? How could I help the system to choose between both ? I tried to put things like : [/usr/local/bin/kdevelop-bin] libpthread.so.2 libpthread.so.1 in libmap.conf, but it does not work for all the programs, and that force me to add a lot of things manually to the libmap.conf file, which is not that good... Thanks ! Gr=E9gory 2007/2/1, Gregory Nou <gregory.nou@gmail.com>: > Hi, > > After trying to figure out how to solve the problem I have on my own, > I'd like to submit it to you, to get some hints. > Here it is: almost all programs related to kde (kdevelop, kghosviewer, > kile, ...) and gaim are segfaulting, because of a problem which seems > to be related to pthread. > Please note that everything else is working fine : xfce-4.4, anjuta, > firefox, etc... > > FreeBSD 7.0-CURRENT #6: Fri Feb 2 13:47:26 EST 2007 > root@greg:/usr/obj/usr/src/sys/MYSMP i386 > > running gdb kile : > > Program received signal SIGSEGV, Segmentation fault. > [Switching to LWP 100060] > 0x29d0f1f9 in pthread_join () from /lib/libpthread.so.2 > (gdb) bt > #0 0x29d0f1f9 in pthread_join () from /lib/libpthread.so.2 > #1 0x29d0374a in pthread_self () from /lib/libpthread.so.2 > #2 0x29d03dfc in pthread_rwlock_unlock () from /lib/libpthread.so.2 > #3 0x29d0f2b2 in pthread_join () from /lib/libpthread.so.2 > #4 0x29d0374a in pthread_self () from /lib/libpthread.so.2 > #5 0x29d03dfc in pthread_rwlock_unlock () from /lib/libpthread.so.2 > #6 0x29d0f2b2 in pthread_join () from /lib/libpthread.so.2 > #7 0x29d0374a in pthread_self () from /lib/libpthread.so.2 > #8 0x29d03dfc in pthread_rwlock_unlock () from /lib/libpthread.so.2 > ... > > and it goes far, repeating it ad vitam. (using ktrace and kdump, wc -l > outputs 637047) > By the way, the equivalent in the ktrace part is : > 2913 kile CALL getpid > 2913 kile RET getpid 2913/0xb61 > 2913 kile CALL getpid > 2913 kile RET getpid 2913/0xb61 > 2913 kile CALL getpid > 2913 kile RET getpid 2913/0xb61 > > Same for kdevelop-bin and all the kde-related who segfault (because > some rare k(something) work, like konsole oder KDE System Guard) > > For gaim, the error message is a bit different, but bt gives the same out= put : > > Program received signal SIGSEGV, Segmentation fault. > [Switching to LWP 100079] > 0x28b38d3e in sysctl () from /lib/libc.so.6 > (gdb) bt > #0 0x28b38d3e in sysctl () from /lib/libc.so.6 > #1 0x28a852b2 in pthread_join () from /lib/libpthread.so.2 > #2 0x28a7974a in pthread_self () from /lib/libpthread.so.2 > #3 0x28a79dfc in pthread_rwlock_unlock () from /lib/libpthread.so.2 > #4 0x28a852b2 in pthread_join () from /lib/libpthread.so.2 > #5 0x28a7974a in pthread_self () from /lib/libpthread.so.2 > #6 0x28a79dfc in pthread_rwlock_unlock () from /lib/libpthread.so.2 > > I experience these problems for more than a week now. Everything is > up-to-date on my system (src + ports) - last cvsup a few hours ago. I > recompiled everything a few time. > As I did not see feedback on forums or on mailing lists, I assume I am > the only one who has this problem. Which makes me feel a bit lonely ;) > > Could you please me help me ? Also, I would be glad to provide any > further information like dmesg, bt, ktrace, whatever, ... > > Thanks ! > Gregory >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85c22ba00702021340k640fd0a2u61f4209c9ebd8315>