Date: Sat, 2 May 2009 18:06:28 +0400 From: Max Brazhnikov <makc@freebsd.org> To: freebsd-stable@freebsd.org Cc: Kostik Belousov <kostikbel@gmail.com> Subject: Re: process hanging on 7.2-PRERELEASE Message-ID: <200905021806.28651.makc@freebsd.org> In-Reply-To: <20090502124516.GE17826@deviant.kiev.zoral.com.ua> References: <200905021443.52526.makc@freebsd.org> <20090502124516.GE17826@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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 0x00000000 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, program=@0xbfbfe5dc, arguments=@0xbfbfe1b4, > > mode=@0xbfbfe1c0) at io/qprocess.cpp:1508 #7 0x08051720 in > > AutoMoc::echoColor (this=0xbfbfe5c8, msg=@0xbfbfe258) at > > /tank/obj/usr/ports/devel/automoc4/work/automoc4-0.9.88/kde4automoc.cpp:7 > >3 #8 0x0804c0a7 in AutoMoc::generateMoc (this=0xbfbfe5c8, > > sourceFile=@0x28714418, mocFileName=@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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905021806.28651.makc>