From owner-freebsd-current@freebsd.org Wed May 24 13:36:09 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7DE0D7A101 for ; Wed, 24 May 2017 13:36:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AF3631DD1 for ; Wed, 24 May 2017 13:36:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AAA66D7A0FF; Wed, 24 May 2017 13:36:09 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA498D7A0FD for ; Wed, 24 May 2017 13:36:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5203B1DCF; Wed, 24 May 2017 13:36:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v4ODZw9t091429 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 May 2017 16:35:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v4ODZw9t091429 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v4ODZwEh091423; Wed, 24 May 2017 16:35:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 24 May 2017 16:35:58 +0300 From: Konstantin Belousov To: David Wolfskill , Dimitry Andric , current@freebsd.org Subject: Re: ino64? r318606 -> r318739 OK; r318739 -> r318781 fails SIGSEGV Message-ID: <20170524133558.GO1622@kib.kiev.ua> References: <20170524121033.GL1622@kib.kiev.ua> <20170524130143.GL1190@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170524130143.GL1190@albert.catwhisker.org> User-Agent: Mutt/1.8.2 (2017-04-18) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2017 13:36:09 -0000 On Wed, May 24, 2017 at 06:01:43AM -0700, David Wolfskill wrote: > On Wed, May 24, 2017 at 02:10:08PM +0200, Dimitry Andric wrote: > > ... > > > building special pic c library > > > --- libc.so.7 --- > > > cc: error: unable to execute command: Segmentation fault (core dumped) > > > cc: error: linker command failed due to signal (use -v to see invocation) > > > *** [libc.so.7] Error code 254 > > > > Looks like your linker is crashing. Can you figure out: > > 1) The exact linker command being run > > 2) The path to the linker executable that crashes > > 3) Backtrace of the crash > > > > -Dimitry > > > > On Wed, May 24, 2017 at 03:10:33PM +0300, Konstantin Belousov wrote: > > ... > > > > If you perform build of r318739 on r318739 (i.e. build of the same sources > > as installed on your machine), does the SIGSEGV occur ? > > > > Anyway, get the core file loaded into gdb and get the backtrace, at least. > > Sorry for the delay; I'm way out of practice with using a debugger... > and I see that gdb isn't in head now. lldb tells me: > > (lldb) bt > * thread #1, name = 'ld', stop reason = signal SIGSEGV > * frame #0: 0x0000000000000000 > (lldb) > > which isn't entirely unexpected, I suppose, given the nature of SIGSEGV. Useful gdb is in ports, devel/gdb. There is nothing in the nature of SIGSEGV which makes lack of the backtrace a reasonable outcome. > > On the build machine, I "cloned" slice 4 to slice 3, then rebooted it > from slice 3, "updated" /usr/src to r318739 and told it to go build > itself (while I continued poking at my laptop). The build machine has > not yet completed the ">>> stage 4.2: building libraries" step -- recall > that I had performed a "make clean" before cloning... -- but it has got > quite a bit beyond the previous point of failure (still building clang). > > I have copied the ld.core and libc.so.7.meta files from the build > machine to (and > made gzipped copies, as well). > > As far as I can tell, the "ld" command was: > freebeast(12.0-C)[10] ls -lT `which ld` > -r-xr-xr-x 2 root wheel 1706336 May 23 05:29:59 2017 /usr/bin/ld > > This, from: > FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #352 r318739M/318739:1200031: Tue May 23 05:16:24 PDT 2017 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC amd64 > > Late note: ">>> stage 4.2: building libraries" has completed on the > build machine (building r318739 while running r318739). > > I apologize for not getting all the information you (both) requested, but > thought it best to provisde what I can (sooner). If build of r318739 succed, can you try, please, to rebuild the current latest sources, but now with reverted r318750 ?