From: j <vwyodapink@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-core] ld segfault cant figure it out
Date: Mon, 16 Apr 2012 15:34:16 -0700 [thread overview]
Message-ID: <4F8C9E68.9050106@gmail.com> (raw)
In-Reply-To: <4F8C9D26.9050500@mlbassoc.com>
On 04/16/2012 03:28 PM, Gary Thomas wrote:
> On 2012-04-16 16:11, j wrote:
>> On 04/13/2012 03:50 PM, j wrote:
>>> On 04/13/2012 03:46 PM, j wrote:
>>>> 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
>>> Sorry forgot the info from qa.log
>>>
>>> libgcc-4.5: non -staticdev package contains static .a library:
>>> libgcc-dev path
>>> '/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcc.a'
>>>
>>> libgcc-4.5: non -staticdev package contains static .a library:
>>> libgcc-dev path
>>> '/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcov.a'
>>>
>>> libgcc-4.5: non -staticdev package contains static .a library:
>>> libgcc-dev path
>>> '/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcc_eh.a'
>>>
>>> bash-4.2: bash: Found a reference to /usr/ in
>>> /home/beagle/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/bash-4.2-r2/packages-split/bash/bin/bashbug
>>>
>>> bash-4.2: Shell scripts in base_bindir and base_sbindir should not
>>> reference anything in exec_prefix
>>>
>>> Any other places to check, as these I do not think relate to a
>>> segfault?
>>
>> I have now tried the build on 3 different OS's the most recent being
>> Arch. All give the same QA log's and all give me segfaults. That are
>> all basically close to the same errors
>> just differing libc versions.
>>
>> I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is
>> causing the segfaults? Is it what is in the QA log?
>>
>>
>>
>> Most current
>> [ 6433.379801] ld[22955]: segfault at 403 ip 00007f703ddcc435 sp
>> 00007fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000]
>> [ 6444.526227] ld[31806]: segfault at 403 ip 00007f0dffc51435 sp
>> 00007fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000]
>>
>> libgcc-4.5: non -staticdev package contains static .a library:
>> libgcc-dev path
>> '/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcc_eh.a'
>>
>> libgcc-4.5: non -staticdev package contains static .a library:
>> libgcc-dev path
>> '/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcc.a'
>>
>> libgcc-4.5: non -staticdev package contains static .a library:
>> libgcc-dev path
>> '/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcov.a'
>>
>> bash-4.2: bash: Found a reference to /usr/ in
>> /home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/bash-4.2-r2/packages-split/bash/bin/bashbug
>>
>> bash-4.2: Shell scripts in base_bindir and base_sbindir should not
>> reference anything in exec_prefix
>>
>>
>> The only reason I am concerned with this and it may be un related is
>> that every time I build task-native-sdk it does not build a working
>> sdk for my device. BB-xm. Yes I know I can
>> install one from the repo, but I want to figure out what is wrong
>> with building one for me.
>>
>> Does anyone have input, advice something?
>
> You've tried different Operating Systems, but one would assume that
> this is all on the same hardware? Have you tried a different build
> host (i.e. hardware/box)?
>
Also it seems to happen around when bitbake starts building gcc-4.5 from
a fresh install that is why I posted the QA info about it.
next prev parent reply other threads:[~2012-04-16 22:44 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 [this message]
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=4F8C9E68.9050106@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