From owner-freebsd-questions@freebsd.org Tue Apr 4 15:55:19 2017 Return-Path: Delivered-To: freebsd-questions@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 40B74D2E80C for ; Tue, 4 Apr 2017 15:55:19 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.home.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fileserver.home.qeng-ho.org", Issuer "fileserver.home.qeng-ho.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B5A9D82C for ; Tue, 4 Apr 2017 15:55:17 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.15.2/8.15.2) with ESMTP id v34FhfD8061276; Tue, 4 Apr 2017 16:43:42 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Subject: Re: Segmentation fault at address 0x818007000 To: Antonio Olivares , FreeBSD Questions References: From: Arthur Chance Message-ID: <790c8e32-0a83-a39b-ed1e-7d18a8aa474f@qeng-ho.org> Date: Tue, 4 Apr 2017 16:43:41 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2017 15:55:19 -0000 On 04/04/2017 16:32, Antonio Olivares wrote: > On Mon, Apr 3, 2017 at 2:30 PM, Antonio Olivares > wrote: >> Dear Folks, >> >> on an 11-RELEASE-p8 amd64 bit machine, updated to latest with pkg >> update and pkg upgrade. Machine was working great. I update to latest >> packages, now I get a segmenation fault. How do I fix this ? I can >> get screenshoot if needed. How does one downgrade Xorg? >> >> Any Ideas? >> >> Thanks, >> >> >> Antonio [cut] > > [ 712.646] (EE) 4: /usr/local/llvm39/lib/libLLVM-3.9.so > (_ZN4llvm13StringMapImpl15LookupBucketForENS_9StringRefE+0xf0) > [0x8094c0340] > > [ 712.651] (EE) 5: /usr/local/llvm39/lib/libLLVM-3.9.so > (LLVMParseCommandLineOptions+0x7cf) [0x80948497f] > > [ 712.656] (EE) 6: /usr/local/llvm39/lib/libLLVM-3.9.so > (LLVMParseCommandLineOptions+0x92c) [0x809484c1c] > > [ 712.660] (EE) 7: /usr/local/llvm39/lib/libLLVM-3.9.so > (_ZN4llvm2cl6Option11addArgumentEv+0x7c) [0x809478dec] > > [ 712.664] (EE) 8: /usr/local/llvm37/lib/libLLVMSupport.so.3.7 > (_ZNSt3__127__insertion_sort_incompleteIRNS_6__lessINS_4pairIN4llvm10TimeRecordENS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEEEESB_EEPSB_EEbT0_SF_T_+0x67d) > [0x817fae31d] > > [ 712.669] (EE) 9: /usr/local/llvm37/lib/libLLVMSupport.so.3.7 > (_ZN4llvm3sys8WatchdogD1Ev+0x32) [0x817fe6264] > > [ 712.673] (EE) 10: /usr/local/llvm37/lib/libLLVMSupport.so.3.7 > (_init+0xe) [0x817f44ebc] [more cut] Notice you have a mix of llvm37 and llvm39 in there. This keeps coming up. You have two versions of llvm present, and X is getting a mix of both, leading to a screwed up runtime system. Delete llvm37 and you should be OK. -- By June 1949, people had begun to realize that it was not so easy to get a program right as had at one time appeared. It was on one of my journeys between the EDSAC room and the punching equipment that the realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs. -- Maurice Wilkes