All of lore.kernel.org
 help / color / mirror / Atom feed
From: j <vwyodapink@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-core] ld segfault cant figure it out
Date: Thu, 19 Apr 2012 17:39:50 -0700	[thread overview]
Message-ID: <4F90B056.5020209@gmail.com> (raw)
In-Reply-To: <CAMKF1spNs63FypJRj332WJzwL9M_eoMFqbiVYzM7BLCim6-9MQ@mail.gmail.com>

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.

Thanks again for the help



  reply	other threads:[~2012-04-20  0:49 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 [this message]
2012-04-20 11:13                                         ` Gary Thomas
2012-04-20 16:17                                           ` j
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=4F90B056.5020209@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.