Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: j <vwyodapink@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: ld segfault cant figure it out
Date: Fri, 13 Apr 2012 15:46:38 -0700	[thread overview]
Message-ID: <4F88ACCE.1030202@gmail.com> (raw)

There seems to be a couple of packages when I build that cause ld 
segfaults such as
[ 6635.846581] ld[14419]: segfault at 8 ip 0077f1bf sp bfbf4a8c error 4 
in libc-2.13.so[73d000+15c000]
[ 6656.831878] ld[20772]: segfault at 8 ip 00ba61bf sp bfaf1bfc error 4 
in libc-2.13.so[b64000+15c000]

I can not seem to be able to track down the package/packages that are 
causing this. I have tried with a clean build dir and only building nano 
and I get it so it is something in the getting environment ready steps. 
Is there a way I can easily track down the build/builds that are causing 
this? Am I even on the right track in this thinking? Nothing fails to 
build and other than task-native-sdk all result in what seem to be 
working packages.

Any info on what or how to figure it out would be greatly appreciated.
building for bbxm on 11.04(uptodate), build environment setup with 
Angstrom scripts and all is up to date.

Thank you



             reply	other threads:[~2012-04-13 22:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 22:46 j [this message]
2012-04-13 22:50 ` ld segfault cant figure it out 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
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=4F88ACCE.1030202@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