Automoc hanging for some FreeBSD users
Thiago Macieira
thiago at kde.org
Wed Nov 24 08:18:40 CET 2010
On Wednesday, 24 de November de 2010 04:13:37 Raphael Kubo da Costa wrote:
> Hi all,
>
> Some FreeBSD users who use -CURRENT (the unstable version) have been
> experiencing some problems while compiling the KDE ports.
>
> automoc seems to hang at random points during compilation. I asked one
> of the users for a backtrace, and it follows below. I'm still clueless
> and don't know for sure if it's something on our side or it's due to
> some FreeBSD bug on libc, for example.
>
> Has anyone ever experienced something like that before?
>
> [Switching to Thread 801c07900 (LWP 100448)]
> 0x0000000801065edc in select () from /lib/libc.so.7
> (gdb) bt
> #0 0x0000000801065edc in select () from /lib/libc.so.7
> #1 0x0000000800e5d4e4 in select () from /lib/libthr.so.3
> #2 0x00000008007cea93 in QProcessManager::run () from
> /usr/local/lib/qt4/libQtCore.so.4 #3 0x00000008006fa649 in
> QThreadPrivate::start () from /usr/local/lib/qt4/libQtCore.so.4 #4
> 0x0000000800e5b2be in pthread_getprio () from /lib/libthr.so.3 #5
> 0x0000000000000000 in ?? ()
> Error accessing memory address 0x7fffffbff000: Bad address.
thr apply all bt
We need the backtrace of the other threads too. The one above is just the
QProcessManager thread (the one that handles SIGCHLD).
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20101124/ddf6522f/attachment.sig
More information about the Kde-buildsystem
mailing list