Hi Matthias, Thanks for the detailed report. The problem you are seeing looks exactly like a problem that was fixed about 10 days ago. Are you sure you are running -current userland?
-Kurt On Monday 03 October 2005 03:00 pm, Matthias Kilian wrote: > Hi, > > when trying to build deve/eclipse, the build hangs after some time. From > eclipse-sdk-3.1p2.log: > > [...] > > | [echo] TARGET: compiler > > [tons of verbose ant blurb] > > | [javac] [total 10074ms] > | [echo] UPDATE ecj.jar > | > | BUILD SUCCESSFUL > | Total time: 15 seconds > | Assuming RHEL CLASSPATH compatible. > | [echo] TARGET: compiler2 > | [echo] compilerArg -encoding ISO-8859-1 > | [echo] build compiler org.eclipse.jdt.core.JDTCompilerAdapter > | [echo] UPDATE ecj.jar > | > | BUILD SUCCESSFUL > | Total time: 13 seconds > | Assuming RHEL CLASSPATH compatible. > | [echo] Deleting jars to recompile... > > At this point, the java process just eats up CPU time. A quick > > ktrace(1)/kdump(1) gives the following: > | 478 java EMUL "native" > | 478 java CALL sigreturn(0xcfbd12ec) > | 478 java RET sigreturn JUSTRETURN > | 478 java PSIG SIGSEGV caught handler=0x8c54e28 mask=0x0 > | addr=0x8293c000 trapno=2 478 java CALL write(0x4,0xcfbd12c7,0x1) > | 478 java RET write -1 errno 35 Resource temporarily unavailable > | 478 java CALL sigreturn(0xcfbd12ec) > | 478 java RET sigreturn JUSTRETURN > | 478 java PSIG SIGSEGV caught handler=0x8c54e28 mask=0x0 > | addr=0x8293c000 trapno=2 > > [...] > > And so on, ad infinitum. > > I'm using a two days old -current (oct. 1th, 15:00 UTC) on i386 and > the following limits: > > time(cpu-seconds) unlimited > file(blocks) unlimited > coredump(blocks) unlimited > data(kbytes) 716800 > stack(kbytes) 32768 > lockedmem(kbytes) 316673 > memory(kbytes) 948592 > nofiles(descriptors) 128 > processes 128 > > malloc.conf is AJFG, USE_SYSTRACE is Yes, but I had the same problem > some days ago an tried with systrace and malloc.conf disabled, > without any success. > > All packages (except eclipse, of course) are uptodate, including > the 1.4 JDK. > > Could anyone please try to reproduce this problem? > > Ciao, > Kili
