Summary: | sys-libs/glibc-2.13-r4 ARM bus error when relocating a misaligned R_ARM_ABS32 relocation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | junkmailnotread |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux | ||
URL: | http://sourceware.org/ml/libc-ports/2011-12/msg00017.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Bug fix for misaligned R_ARM_ABS32 relocation
glibc arm reloc |
Description
junkmailnotread
2011-12-10 12:40:51 UTC
Created attachment 295357 [details, diff]
Bug fix for misaligned R_ARM_ABS32 relocation
Created attachment 295409 [details, diff]
glibc arm reloc
i think that change is more complicated than necessary. try this one instead.
Yes, my fix was just a quick hack. Your simpler one works too. i've committed a patch (which is included in glibc-2.14.1-r2): http://sources.gentoo.org/gentoo/src/patchsets/glibc/2.14.1/6250_all_glibc-2.14-arm-unaligned-reloc.patch?rev=1.1 could you test + confirm that it fixes your issues ? you can put arbitrary patches into /etc/portage/patches/sys-libs/glibc/ to have them applied automatically when emerging glibc. Yes, your 6250 patch fixes it too. Creating /etc/portage/patches/sys-libs/glibc and copying the 6250 patch into it didn't seem to have any affect; dl-machine.h was not modified after the emerge had started. So I manually applied the 6250 patch to glibc-2.13-r4 during emerge. I had re-emerged cross-arm-softfloat-linux-gnueabi/gcc since I first filed this bug, so I verified that the R_ARM_ABS32 relocation is still misaligned: % arm-softfloat-linux-gnueabi-objdump -R /usr/lib/gcc/arm-softfloat-linux-gnueabi/4.5.3/libstdc++.so.6.0.14 | fgrep __gxx_personality_v0 001089db R_ARM_ABS32 __gxx_personality_v0 0012c848 R_ARM_JUMP_SLOT __gxx_personality_v0 % The hello world test program works OK with the patched glibc-2.13-r4. thanks for verifying. i'll send it upstream then. |