From: j <vwyodapink@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-core] ld segfault cant figure it out
Date: Fri, 20 Apr 2012 09:17:18 -0700 [thread overview]
Message-ID: <4F918C0E.4040107@gmail.com> (raw)
In-Reply-To: <4F9144BE.1070508@mlbassoc.com>
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<vwyodapink@gmail.com> 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?
next prev parent reply other threads:[~2012-04-20 16:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 22:46 ld segfault cant figure it out j
2012-04-13 22:50 ` j
2012-04-16 22:11 ` [oe-core] " j
2012-04-16 22:28 ` Gary Thomas
2012-04-16 22:32 ` j
2012-04-16 22:41 ` Gary Thomas
2012-04-16 22:54 ` j
2012-04-16 22:34 ` j
2012-04-17 1:43 ` j
2012-04-17 15:41 ` J. L.
2012-04-17 15:54 ` Gary Thomas
2012-04-17 16:11 ` J. L.
2012-04-17 16:13 ` J. L.
2012-04-17 19:09 ` j
2012-04-17 19:34 ` Mark Hatle
2012-04-17 19:49 ` j
2012-04-17 20:17 ` j
2012-04-17 21:16 ` j
2012-04-18 0:37 ` j
2012-04-18 5:30 ` Khem Raj
2012-04-18 5:40 ` j
2012-04-18 22:00 ` Khem Raj
2012-04-19 3:32 ` j
2012-04-19 6:24 ` Khem Raj
2012-04-20 0:39 ` j
2012-04-20 11:13 ` Gary Thomas
2012-04-20 16:17 ` j [this message]
2012-04-20 18:03 ` j
2012-04-21 21:47 ` [oe-core] 3 build machines all failing in the same manner - was:ld " j
2012-04-24 20:39 ` j
2012-04-24 20:44 ` Phil Blundell
2012-04-24 20:57 ` j
2012-04-24 20:57 ` j
2012-04-24 21:03 ` Phil Blundell
2012-04-24 21:15 ` j
2012-04-27 17:16 ` j
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F918C0E.4040107@gmail.com \
--to=vwyodapink@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.