Openembedded Devel Discussions
 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: Tue, 17 Apr 2012 22:40:45 -0700	[thread overview]
Message-ID: <4F8E53DD.6060404@gmail.com> (raw)
In-Reply-To: <CAMKF1sqys83Vu1pv-_3r-RpUe894vQrwpJ1K7NCsyfHXb8vBYA@mail.gmail.com>

On 04/17/2012 10:30 PM, Khem Raj wrote:
> On Tue, Apr 17, 2012 at 5:37 PM, j<vwyodapink@gmail.com>  wrote:
>> Well finally caught what I think is the package the segfault kicks on expat.
>> Though not sure what I should look for to be able to sort it out but will
>> see where I get.
>>
>> Though I still get the gcc and bash messages in the QA log. If anyone is
>> willing to share some info on what or how I can figure out how to find what
>> causes the segfault in the recipe or if I am even catching the correct one.
>>
> you are not giving out enough information. Looking at dmesg is not
> going to give much info
> if ld segfaults which I assume is cross ld here then the corresponding
> recipe should fail
> and then you should look in the build of that package and the commands
> causing the segfaults
> should be in log.do_compile or log.do_install.
>
> Thanks
> -Khem
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
See thats the thing no recipe is failing but the system segfaults. The 
resulting images have had quirks which is what led me to trying to sort 
out the segfault issue.

Sorry to sound so dumb but if there is no recipe failing and 2 separate 
systems are segfaulting in similar manners and both result with not 
fully functioning images/packages where else can I look for info? I 
posted all the logs to one of the builds, and the QA log seems to be the 
only thing really spitting out anything. I am open to trying and or 
sharing any and all relevant info to help sort it out or get me on track 
to sorting it out.

Thank you for all the continued effort.



  reply	other threads:[~2012-04-18  5:50 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 [this message]
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
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=4F8E53DD.6060404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox