From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yw0-f47.google.com ([209.85.213.47]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SLGfl-0003SR-Mq for openembedded-devel@lists.openembedded.org; Fri, 20 Apr 2012 18:27:01 +0200 Received: by yhjj56 with SMTP id j56so5367359yhj.6 for ; Fri, 20 Apr 2012 09:17:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=B7K29RriIjpJa43pfg/DQusg7xlVvKh5/YIdfG0BX28=; b=QXMbg3Tx07Wb8iblLRSMVVx8gv3cuo1bWGDEiPzvjDzxEaJUS1JvsliM3qZp62R7Ij fvcITKPJ/ZS4sfdoAjogzvqJWOxnOusIbS7vUgbC7kumMcO+xKuBTx2ECwK0Ejaa9qkD hDulOE52wBMVVb/7P5+w4tB+AQCBMK8ikYglkqXg6xDZb3w9BnQv6ghZkegbCspHUCmv Ixxder3zbCW16DkJEbUOH/yofWsmqBmqH4sZYGUTHEgfvi2eZTEjhDPkPM+ZFxShu9ei 77kL20NHKAM3kjAP+1pKURBUmpgPjeZ6w68WbqcEWaY4cu+GnGpzxx2is94FSf10j2Qw eQhA== Received: by 10.236.190.39 with SMTP id d27mr6371154yhn.57.1334938651396; Fri, 20 Apr 2012 09:17:31 -0700 (PDT) Received: from [192.168.1.3] (dpc674485156.direcpc.com. [67.44.85.156]) by mx.google.com with ESMTPS id i7sm4210044ani.17.2012.04.20.09.17.25 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 09:17:30 -0700 (PDT) Message-ID: <4F918C0E.4040107@gmail.com> Date: Fri, 20 Apr 2012 09:17:18 -0700 From: j User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120406 Thunderbird/11.0.1 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4F88ACCE.1030202@gmail.com> <4F88ADA3.5030804@gmail.com> <4F8C9902.8020904@gmail.com> <4F8C9D26.9050500@mlbassoc.com> <4F8C9E68.9050106@gmail.com> <4F8CCAAA.6050406@gmail.com> <4F8D9245.3080908@mlbassoc.com> <4F8DBFF3.2060508@gmail.com> <4F8DC5B5.600@windriver.com> <4F8DC939.90208@gmail.com> <4F8DCFC4.9010508@gmail.com> <4F8DDDB7.5010605@gmail.com> <4F8E0CDF.6040401@gmail.com> <4F8E53DD.6060404@gmail.com> <4F8F8749.8000803@gmail.com> <4F90B056.5020209@gmail.com> <4F9144BE.1070508@mlbassoc.com> In-Reply-To: <4F9144BE.1070508@mlbassoc.com> Subject: Re: [oe-core] ld segfault cant figure it out X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 16:27:02 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/20/2012 04:13 AM, Gary Thomas wrote: > On 2012-04-19 18:39, j wrote: >> On 04/18/2012 11:24 PM, Khem Raj wrote: >>> On Wed, Apr 18, 2012 at 8:32 PM, j wrote: >>>>> on ubuntu edit /etc/security/limits.conf on build host and then add >>>>> * soft core unlimited >>> >>> btw. reboot your machine after this change is made >>> >>>>> that should generate core files. After this search for core* files in >>>>> build tree >>>>> and see if there are any then debug them with gdb to diagnose it >>>>> further >>>>> >>>>> Now I am not sure if those segfaults directly relate to >>>>> malfunction of >>>>> image >>>>> if thats the case but its likely. You should also try to explore the >>>>> reasons why >>>>> the image fails to behave as expected. >>>> I will do as suggested as well as do a full image build again and >>>> see if I >>>> can find out all that is not working. Thank you for the extra >>>> debugging info >>>> and suggestions. Are there any keywords to search through all the >>>> files for >>>> including the normal log files, it may help me track down things even >>>> further. >>> _______________________________________________ >>> Openembedded-devel mailing list >>> Openembedded-devel@lists.openembedded.org >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel >> >> did the reboot went through the build but yet did not produce any >> core files. But I noticed ulimit was still 0 so changed it to >> unlimited now and building again, hopefully that >> will get some core dumps. Will post back once I have more info and >> will separate anything by which machine as even the 2nd borrowed >> machine segfaults in the same way. > > Is your borrowed machine also running ArchLinux? If so, have > you tried anything else - Ubuntu, Fedora, etc? As far as I can > tell, you're the only one suffering these problems and also you > seem to be the only one using ArchLinux. I have installed Ubuntu 10.04 and Fedora 16 on the borrowed machine as well. And still failing in the same manner. I am trying to do what Khem suggested and get core files but for some reason, even though it is saying I have it set to unlimited it is still not spitting anything out. I have abandoned Arch on the build machines for now as to keep that out of the variables. > > Note: I tried to duplicate your problems here, but I've never used > ArchLinux and it's so primitive and hard to use (compared to what > I use everyday) that I simply don't have the time to mess with it > any more. > It is not the only OS that does this for me. I am honestly surprised to hear Arch is hard, as that is how I see OE and trying to get a functioning build machine. :P I just got my 2nd borrowed machine today and starting to set it up now. Installing Ubuntu on it. If there is a single OS to install and try on all 3 I will happily do it again. But this is a non OS dependent thing is my guess since I am on 2 machines now that have done this. My QA.log's are still basically the same as well. all relating to LD type issues. I am still working through getting the image built on th1st borrowed machine it is slow and starting the Again OE classic(gumstix branch does not segfault on my machine that started all this it only started happening once I started trying to build a BBXM image on a new install on the same machine. If there is a OS and configuration to specifically try then outside of what is listed on the Angstrom pages and OE and your Distro pages please fill me in and will try. But as it stands now 2 totally different machines have gone through 3+ OS changes all have the same issue, all relatively the same issues and logs that were posted before. Should I attach more logs?