From owner-freebsd-current Thu Jul 18 10:40:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE3CE37B400 for ; Thu, 18 Jul 2002 10:40:52 -0700 (PDT) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id C36E543E65 for ; Thu, 18 Jul 2002 10:40:44 -0700 (PDT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.12.5/8.12.5) with ESMTP id g6IHeipI004752 for ; Thu, 18 Jul 2002 10:40:44 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.5/8.12.5/Submit) id g6IHeioF004751 for current@freebsd.org; Thu, 18 Jul 2002 10:40:44 -0700 (PDT) Date: Thu, 18 Jul 2002 10:40:44 -0700 (PDT) From: David Wolfskill Message-Id: <200207181740.g6IHeioF004751@bunrab.catwhisker.org> To: current@freebsd.org Subject: ld hanging during build of today's -CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK; I built today's -CURRENT (running yesterday's, as usual) on my SMP build machine without incident earlier today. And, as usual, I'm trying the same thing with my (UP) laptop. But this time, the sequence has come to a halt; here's what I see so far: >>> stage 4: populating /usr/obj/usr/src/i386/usr/include ... >>> stage 4: building libraries ... ===> gnu/lib/libobjc ... ===> gnu/lib/libg2c cc -O -pipe -DLIBC_MAJOR=5 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -D__DBINTERFACE_PRIVATE -DINET6 -I/common/S3/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -DYP -DHESIOD -c nslexer.c -o nslexer.o cc -pg -O -pipe -DLIBC_MAJOR=5 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -D__DBINTERFACE_PRIVATE -DINET6 -I/common/S3/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -DYP -DHESIOD -c nslexer.c -o nslexer.po cc -fpic -DPIC -O -pipe -DLIBC_MAJOR=5 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -D__DBINTERFACE_PRIVATE -DINET6 -I/common/S3/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -DYP -DHESIOD -c nslexer.c -o nslexer.So building profiled c library building shared library libc.so.5 building special pic c library building static c library ranlib libc_pic.a ranlib libc.a ranlib libc_p.a and at this point, ^T says: load: 0.00 cmd: ld 64393 [inode] 0.10u 0.30s 0% 1k "ps -xwwlp 64393" says: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 64393 64391 0 96 0 12108 2925 - W+ p7 0:00.41 (ld) and various bits and pieces of /proc/64393 say: g1-9(5.0-C)[10] sudo cat /proc/64393/map 0x8048000 0x80c8000 48 48 0xc20ca4b0 r-x 2 1 0x0 COW NC vnode 0x80c8000 0x80c9000 1 0 0xc1d7cf3c rw- 1 0 0x2180 COW NNC vnode 0x80c9000 0x80cd000 3 0 0xc1fd6af0 rw- 2 0 0x2180 NCOW NNC default 0x80cd000 0x8bf7000 2856 0 0xc1fd6af0 rwx 2 0 0x2180 NCOW NNC default 0x280cb000 0x280cf000 3 0 0xc1e58e74 rwx 1 0 0x2180 NCOW NNC default 0xbfbe0000 0xbfc00000 6 0 0xc1afd7d0 rwx 1 0 0x2180 NCOW NNC default g1-9(5.0-C)[13] sudo cat /proc/64393/status ld 64393 64391 594 576 5,7 ctty 1027012600,166143 0,101735 0,305207 nochan 0 0 0,0,0,2,3,4,5,20,31 - g1-9(5.0-C)[15] sudo cat /proc/64393/rlimit cpu -1 -1 fsize -1 -1 data 536870912 536870912 stack 67108864 67108864 core -1 -1 rss -1 -1 memlock -1 -1 nproc 896 896 nofile 1792 1792 sbsize -1 -1 vmem -1 -1 Now, I'm running the "make buildworld" with -j4 (as usual, for the laptop). I rather suspect that were I to interrupt & restart it, this hang probably would not recur (at least, not in exactly this way). So I'm sending this out now, in the hope that someone might suggest some approach(es) that might cause the system to divulge what happened, so we can prevent a recurrence of this sort of thing. Unfortunately, I don't seem to have built this kernel with BREAK_TO_DEBUGGER. :-( So -- is this worth pursuing, or should I just muddle on through? Thanks, david -- David H. Wolfskill david@catwhisker.org My reluctance to use or support Microsoft products is a direct consequence of my desire to use tools that work properly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message