automoc4 processes lock again
Hi, After recent Qt-4.7.3 update I can't build KDE4 ports anymore (tested on 8.2-STABLE amd64 only). The problem is always reproduced with x11/kdelibs4. The build stalls with hanging automoc4 processes. Any help is appreciated. # ps | grep automoc 18636 3 IN+0:00.02 /usr/local/bin/automoc4 /usr/obj/usr/local/tinderbox/portstrees/FreeBSD/ports/x11/kdelibs4/work/kdelibs-4.6.3/build/kde3support/ 18640 3 IN+0:00.00 /usr/local/bin/automoc4 /usr/obj/usr/local/tinderbox/portstrees/FreeBSD/ports/x11/kdelibs4/work/kdelibs-4.6.3/build/kde3support/ # gdb automoc4 18636 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Attaching to program: /usr/local/bin/automoc4, process 18636 Reading symbols from /usr/local/lib/qt4/libQtCore.so.4...Reading symbols from /usr/local/lib/qt4/libQtCore.so.4.7.3.debug...done. done. Loaded symbols for /usr/local/lib/qt4/libQtCore.so.4 Reading symbols from /usr/lib/libstdc++.so.6...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /lib/libz.so.5...done. Loaded symbols for /lib/libz.so.5 Reading symbols from /usr/local/lib/libgthread-2.0.so.0...done. Loaded symbols for /usr/local/lib/libgthread-2.0.so.0 Reading symbols from /usr/local/lib/libglib-2.0.so.0...done. Loaded symbols for /usr/local/lib/libglib-2.0.so.0 Reading symbols from /usr/local/lib/libiconv.so.3...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libthr.so.3...done. [New Thread 801c0ae40 (LWP 100660/automoc4)] [New Thread 801c041c0 (LWP 100590/initial thread)] Loaded symbols for /lib/libthr.so.3 Reading symbols from /usr/local/lib/libintl.so.9...done. Loaded symbols for /usr/local/lib/libintl.so.9 Reading symbols from /usr/local/lib/libpcre.so.0...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 [Switching to Thread 801c0ae40 (LWP 100660/automoc4)] 0x00080104c99c in select () at select.S:3 3 RSYSCALL(select) (gdb) bt #0 0x00080104c99c in select () at select.S:3 #1 0x0008008502cd in QProcessManager::run (this=0x800b196e0) at io/qprocess_unix.cpp:245 #2 0x000800749bde in QThreadPrivate::start (arg=0x800b196e0) at thread/qthread_unix.cpp:320 #3 0x0008017985e1 in thread_start (curthread=0x801c0ae40) at /usr/freebsd/8/src/lib/libthr/thread/thr_create.c:288 #4 0x in ?? () Error accessing memory address 0x7fbff000: Bad address. Current language: auto; currently asm # gdb automoc4 18640 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Attaching to program: /usr/local/bin/automoc4, process 18640 Reading symbols from /usr/local/lib/qt4/libQtCore.so.4...Reading symbols from /usr/local/lib/qt4/libQtCore.so.4.7.3.debug...done. done. Loaded symbols for /usr/local/lib/qt4/libQtCore.so.4 Reading symbols from /usr/lib/libstdc++.so.6...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /lib/libz.so.5...done. Loaded symbols for /lib/libz.so.5 Reading symbols from /usr/local/lib/libgthread-2.0.so.0...done. Loaded symbols for /usr/local/lib/libgthread-2.0.so.0 Reading symbols from /usr/local/lib/libglib-2.0.so.0...done. Loaded symbols for /usr/local/lib/libglib-2.0.so.0 Reading symbols from /usr/local/lib/libiconv.so.3...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libthr.so.3...done. Error while reading shared library symbols: Cannot get thread info: invalid key Reading symbols from /usr/local/lib/libintl.so.9...done. Loaded symbols for /usr/local/lib/libintl.so.9 Reading symbols from /usr/local/lib/libpcre.so.0...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 0x0008017a24cc in _umtx_op_err () at /usr/freebsd/8/src/l
Re: automoc4 processes lock again
On Mon, 9 May 2011 15:41:05 +0300, Kostik Belousov wrote: > You did not supplied enough information. > Which of the processes is parent, which is child ? > Note that there are other threads in the pid 18636. What does they do ? Here is backtraces from all threads http://people.freebsd.org/~makc/automoc4.bt 63373 is a parent now, 63374 is a child. There were no related changes in Qt4 and automoc4 sources, probably my update from 8.2-PRERELEASE to STABLE a week ago triggered the issue. > If you would allow me to make some guess, then I could assume that pid > 18640 is the child. Note that the child is waiting for the pthread > mutex locked which protects the stdio' FILE structure. Now, assume > additionally that the parent had the FILE locked in one thread while > another thread did the fork. Then, the child process would never be able > to obtain the lock because the lock was acquired by the thread that > exists no longer (in the child process, only the thread that called > fork is duplicated). > > In fact, I believe that you already reported a similar problem with > malloc(3) some time ago. The root of the problem would be an undefined > (and permitted by POSIX) behaviour of calling non-async signal safe > functions in multithreaded process after fork. > > For malloc(3), this can be argued to be a quality of the implementation > issue, but there is no reason to specially handle random mutexes, even > from libc. If the mutex was locked during the fork time, the protected > data structure is arguably in the inconsistent state after the fork in > the child. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can't update libzip-0.9.3 to libzip-0.10
On Thu, 12 May 2011 09:54:06 +0200, Michael Ross wrote: > Am 12.05.2011, 08:59 Uhr, schrieb Jeremy Chadwick > : > > > > > Are you using any sort of LC_CTYPE or LANG setting in your dotfiles that > > gets propagated to the root environment (during su, sudo, etc.)? I see > > that you're in .de which is why I ask. > > I have > > :lang=de_DE.ISO8859-1:\ > > in /etc/login.conf. > > Soon as I remove this, libzip compiles without error. > > Generated zipconf.h: http://pastebin.com/n8YKaNQ8 > > > For comparison, with lang=de, > completelty different types detected and used, > erroneous zipconf.h: http://pastebin.com/yTw77zgt Thank you all, I've just fixed lipzip port. Max ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_8 -- shutdown -p no longer powers off boxes
On Thu, 22 Apr 2010 07:35:42 -0700, Jeremy Chadwick wrote: > Looks like some form of regression in RELENG_8, between the dates of > 2010/03/30 and 2010/04/22. My 2010/03/30 kernel (built from RELENG_8 > source dated 2010/03/30 @ 10:30 PDT) doesn't have this problem. Does not work for me either since I updated my system on April 4. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
process hanging on 7.2-PRERELEASE
Currently all kde4 ports marked as jobs_unsafe, because of automoc4 hangs. The problem can be easely reproduced building e.g. accessibility/kdeaccessibility4 with multiple jobs: replace MAKE_JOBS_UNSAFE with MAKE_JOBS_SAFE in port Makefile and run 'make MAKE_JOBS_NUMBER=16'. Build will be freezed on /usr/local/bin/cmake -E cmake_progress_report /tank/obj/usr/ports/accessibility/kdeaccessibility4/work/kdeaccessibility-4.2.2/build/CMakeFiles 77 78 79 8081 82 83 84 85 86 87 88 89 90 91 92 93 94 95 [ 95%] Built target kmouth # ps | grep automoc4 77829 p4 S+ 0:00.27 /usr/local/bin/automoc4 /tank/obj/usr/ports/accessibility/kdeaccessibility4/ 77840 p4 I+ 0:00.00 /usr/local/bin/automoc4 /tank/obj/usr/ports/accessibility/kdeaccessibility4/ #gdb66 automoc4 77829 GNU gdb 6.6 [GDB v6.6 for FreeBSD] Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-portbld-freebsd7.0"... Attaching to program: /usr/local/bin/automoc4, process 77829 Reading symbols from /usr/local/lib/qt4/libQtCore.so.4...Reading symbols from /usr/local/lib/qt4/libQtCore.so.4.4.3.debug...done. done. Loaded symbols for /usr/local/lib/qt4/libQtCore.so.4 Reading symbols from /usr/lib/libstdc++.so.6...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libthr.so.3...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /lib/libz.so.4...done. Loaded symbols for /lib/libz.so.4 Reading symbols from /usr/local/lib/libgthread-2.0.so.0...done. Loaded symbols for /usr/local/lib/libgthread-2.0.so.0 Reading symbols from /usr/local/lib/libglib-2.0.so.0...done. Loaded symbols for /usr/local/lib/libglib-2.0.so.0 Reading symbols from /usr/local/lib/libiconv.so.3...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /usr/local/lib/libintl.so.8...done. Loaded symbols for /usr/local/lib/libintl.so.8 Reading symbols from /usr/local/lib/libpcre.so.0...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 0x2846fb3b in select () at select.S:2 2 RSYSCALL(select) (gdb) bt #0 0x2846fb3b in select () at select.S:2 #1 0x2838d788 in __select (numfds=6, readfds=0xbf9feee8, writefds=0x0, exceptfds=0x0, timeout=0x0) at /usr/freebsd/7/src/lib/libthr/thread/thr_syscalls.c:444 #2 0x281b4f3d in QProcessManager::run (this=0x287142f0) at io/qprocess_unix.cpp:301 #3 0x280f30e2 in QThreadPrivate::start (arg=0x287142f0) at thread/qthread_unix.cpp:185 #4 0x2838b68a in thread_start (curthread=0x28701150) at /usr/freebsd/7/src/lib/libthr/thread/thr_create.c:288 #5 0x in ?? () Current language: auto; currently asm (gdb) # gdb66 automoc4 77840 GNU gdb 6.6 [GDB v6.6 for FreeBSD] Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for deta
Re: process hanging on 7.2-PRERELEASE
On Sat, 2 May 2009 15:45:17 +0300, Kostik Belousov wrote: > On Sat, May 02, 2009 at 02:43:52PM +0400, Max Brazhnikov wrote: > > Currently all kde4 ports marked as jobs_unsafe, because of automoc4 > > hangs. The problem can be easely reproduced building e.g. > > accessibility/kdeaccessibility4 with multiple jobs: replace > > MAKE_JOBS_UNSAFE with MAKE_JOBS_SAFE in port Makefile and run 'make > > MAKE_JOBS_NUMBER=16'. Build will be freezed on > > > > /usr/local/bin/cmake -E cmake_progress_report > > /tank/obj/usr/ports/accessibility/kdeaccessibility4/work/kdeaccessibility > >-4.2.2/build/CMakeFiles 77 78 79 8081 82 83 84 85 86 87 88 89 90 91 92 93 > > 94 95 > > [ 95%] Built target kmouth > > > > # ps | grep automoc4 > > 77829 p4 S+ 0:00.27 /usr/local/bin/automoc4 > > /tank/obj/usr/ports/accessibility/kdeaccessibility4/ 77840 p4 I+ > > 0:00.00 /usr/local/bin/automoc4 > > /tank/obj/usr/ports/accessibility/kdeaccessibility4/ > > > > #gdb66 automoc4 77829 > > 0x2846fb3b in select () at select.S:2 > > 2 RSYSCALL(select) > > (gdb) bt > > #0 0x2846fb3b in select () at select.S:2 > > #1 0x2838d788 in __select (numfds=6, readfds=0xbf9feee8, writefds=0x0, > > exceptfds=0x0, timeout=0x0) at > > /usr/freebsd/7/src/lib/libthr/thread/thr_syscalls.c:444 > > #2 0x281b4f3d in QProcessManager::run (this=0x287142f0) at > > io/qprocess_unix.cpp:301 #3 0x280f30e2 in QThreadPrivate::start > > (arg=0x287142f0) at thread/qthread_unix.cpp:185 #4 0x2838b68a in > > thread_start (curthread=0x28701150) at > > /usr/freebsd/7/src/lib/libthr/thread/thr_create.c:288 #5 0x in > > ?? () > > Current language: auto; currently asm > > (gdb) > > > > > > # gdb66 automoc4 77840 > > 0x28395593 in _umtx_op_err () at > > /usr/freebsd/7/src/lib/libthr/arch/i386/i386/_umtx_op_err.S:36 36 > > SYSCALL_ERR(_umtx_op) > > (gdb) bt > > #0 0x28395593 in _umtx_op_err () at > > /usr/freebsd/7/src/lib/libthr/arch/i386/i386/_umtx_op_err.S:36 #1 > > 0x283953c4 in __thr_umutex_lock (mtx=0x8054f3c, id=100416) at > > /usr/freebsd/7/src/lib/libthr/thread/thr_umtx.c:58 #2 0x28390502 in > > mutex_lock_sleep (curthread=0x28701040, m=0x8054f3c, abstime=0x0) at > > /usr/freebsd/7/src/lib/libthr/thread/thr_mutex.c:401 #3 0x283fb0ea in > > _malloc_postfork () at /usr/freebsd/7/src/lib/libc/stdlib/malloc.c:1029 > > #4 0x28393038 in _fork () at > > /usr/freebsd/7/src/lib/libthr/thread/thr_fork.c:178 #5 0x281b7381 in > > QProcessPrivate::startProcess (this=0x287720f0) at > > io/qprocess_unix.cpp:570 #6 0x2817a181 in QProcess::start > > (this=0xbfbfe1b8, progr...@0xbfbfe5dc, argumen...@0xbfbfe1b4, > > mo...@0xbfbfe1c0) at io/qprocess.cpp:1508 #7 0x08051720 in > > AutoMoc::echoColor (this=0xbfbfe5c8, m...@0xbfbfe258) at > > /tank/obj/usr/ports/devel/automoc4/work/automoc4-0.9.88/kde4automoc.cpp:7 > >3 #8 0x0804c0a7 in AutoMoc::generateMoc (this=0xbfbfe5c8, > > sourcefi...@0x28714418, mocfilena...@0x2871441c) at > > /tank/obj/usr/ports/devel/automoc4/work/automoc4-0.9.88/kde4automoc.cpp:5 > >69 #9 0x0804f4ae in AutoMoc::run (this=0xbfbfe5c8) at > > /tank/obj/usr/ports/devel/automoc4/work/automoc4-0.9.88/kde4automoc.cpp:4 > >70 #10 0x080504e6 in main (argc=Cannot access memory at address 0x0 ) at > > /tank/obj/usr/ports/devel/automoc4/work/automoc4-0.9.88/kde4automoc.cpp:1 > >14 Current language: auto; currently asm > > (gdb) > > Great. > > I think this is a missed merge of the r185514 to 7. Can you, please, > retest with that revision merged ? Great! With the patch I can't reproduce the problem! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
