[oe] [oe-core] ld segfault cant figure it out

j vwyodapink at gmail.com
Mon Apr 16 22:11:14 UTC 2012


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?




More information about the Openembedded-devel mailing list