From owner-freebsd-arm@freebsd.org Tue Apr 19 13:26:34 2016 Return-Path: Delivered-To: freebsd-arm@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 5F5AFB140AE for ; Tue, 19 Apr 2016 13:26:34 +0000 (UTC) (envelope-from carpeddiem@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 40D421462 for ; Tue, 19 Apr 2016 13:26:34 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 40196B140AD; Tue, 19 Apr 2016 13:26:34 +0000 (UTC) Delivered-To: arm@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 3FBFAB140AC for ; Tue, 19 Apr 2016 13:26:34 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BC43145E for ; Tue, 19 Apr 2016 13:26:34 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-ig0-x233.google.com with SMTP id gy3so19710717igb.1 for ; Tue, 19 Apr 2016 06:26:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=RA7Ffj6MwAhCrx8rLfFDiBIKLCOWdRBsJxisRNSff0w=; b=B2QNAGot2E9qeX5uxqeNL7lrK+R3qbCPjq8tkixqib8ANFQsh6iRJetGvDsWEk+h1A AOtEfdN1POJk0hqi9XDrkNbcOw3aDz+68dxozmtAFl0qEQaySH/ke8HyX1+neBWqKbID c+OgFU2JY8RweeGkU0+4OmL9DQJLPFviPwp9On5m/UeK8lHCA4gG9Gz/C9sj28fVW69Q wBBpt6SscKHKgxDxFgynLhfuKRWsUshMnVtXT+mepTthrFit5nQU8N1KxG26elBbo7vK gyhqXme4CiY+TEEjUD1wVSerj7hHiUiSdXl6JyT8fZmaNY78Hh0ntuPdbseWMMiYLzdi M14g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=RA7Ffj6MwAhCrx8rLfFDiBIKLCOWdRBsJxisRNSff0w=; b=HDTtXgo2ocfQJjab1Unahevq6dgp36/n+0zZndvfmhDh3LyjwoRedaLwxpouvzvs4h woBr86L2SCIXuyCsMIWbq03Kx9BgOe50/GG65+XRbabD7dFVdhd9iCO0SkebEaxjQLQ9 UO4HpBUxQFGdAEvHCqsQuDb0DWtQDs4WV7W3ovxTBpYe6ht60ryTcJVmmq8ejZajs+2r wAwsdRzmp7YKZzHrTreiMEES2BNDzAYY+Metw13rP6oHklSHuypuSu5zSaKGqSDaGtWQ u8DgTZ0WS7Gc3dGNdvYznCivlh2PDjDvMfcHCZmUFk/E0lXVCSasFrfQkIKc5P8szryD trUQ== X-Gm-Message-State: AOPr4FXR6soiveswwOecxQX2rAGW3/gH/qxYY5E06BGrOwom/dhf9Zw0Lv6aFhXqk+vULBEi1ifC6SZ2LUcv3w== X-Received: by 10.50.6.110 with SMTP id z14mr24255516igz.33.1461072393464; Tue, 19 Apr 2016 06:26:33 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.9.224 with HTTP; Tue, 19 Apr 2016 06:26:13 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Tue, 19 Apr 2016 09:26:13 -0400 X-Google-Sender-Auth: eF4m9mKrysQ9MkbXHv0OFO80g1A Message-ID: Subject: Re: ARM64 buildworld failure on ThunderX To: Wojciech Macek Cc: "freebsd-arm@freebsd.org" , arm64-dev Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2016 13:26:34 -0000 On 22 March 2016 at 08:34, Wojciech Macek wrote: > Hello, > > I was debugging strange userspace crashes during native aarch64 buildworld, > and I think that it is highly probable that they are caused by issues with > recent toolchain or system libraries. > The same test as below, but run on older sources (the one with clang-3.6) is > just fine, build succeeds and soelim does not crash. > > I'd like to get some feedback if anyone do or did see similar behavior or > how this might be pushed forward. I can provide binaries, logs and whatever > is necessary. > > The application that fails is a soelim (in about 95% of all cases): > > --- be_BY.CP1131.LC_CTYPE --- > --- all_subdir_share/doc --- > --- all_subdir_share/doc/usd --- > groff: soelim: Signal 11 (core dumped) > --- all_subdir_share/i18n --- > sed "s/CPx/CP10007/" /root/freebsd-arm64/share/i18n/esdb/CP/CP.src > > CP10007.src > --- all_subdir_share/i18n/csmapper --- > --- UCS%CP950.mps --- > --- all_subdir_share/ctypedef --- > > > > When I try to manually call the application, it coredumps too. > > root@thunder_crb4:~/freebsd-arm64 # find /usr/obj/ -name soelim > /usr/obj/root/freebsd-arm64/tmp/usr/lib/debug/usr/tests/usr.bin/soelim > /usr/obj/root/freebsd-arm64/tmp/usr/tests/usr.bin/soelim > /usr/obj/root/freebsd-arm64/tmp/legacy/usr/bin/soelim > /usr/obj/root/freebsd-arm64/tmp/root/freebsd-arm64/usr.bin/soelim > /usr/obj/root/freebsd-arm64/tmp/root/freebsd-arm64/usr.bin/soelim/soelim > /usr/obj/root/freebsd-arm64/usr.bin/soelim > root@thunder_crb4:~/freebsd-arm64 # > /usr/obj/root/freebsd-arm64/tmp/root/freebsd-arm64/usr.bin/soelim/soelim > Segmentation fault (core dumped) > root@thunder_crb4:~/freebsd-arm64 # > > > Steps to reproduce: > 1. Clone the FreeBSD HEAD > 2. Call "make buildworld -j48 -DNO_CLEAN" > 3. Relax and wait for the crash to happen... Can you make the usr.bin/soelim directory available somewhere? My soelim doesn't crash when run by itself: root@cavium:~ # /usr/obj/usr/src/usr.bin/soelim/soelim root@cavium:~ # After keeping a copy, what happens if you clean the usr.bin/soelim directory and try again? With -NO_CLEAN it's not going to rebuild soelim and then segfault each time, of course.