Summary: | xine-lib TEXTREL in xineplug_decode_mpeg2.so with USE altivec | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Steffen <verbuggt> |
Component: | New packages | Assignee: | PPC Porters <ppc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flameeyes, hardened, pageexec |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Steffen
2006-05-28 06:33:47 UTC
Till gentoo/ppc takes the secure plt patches there is probably not much point in exploring this. TEXTREL's are pretty much write operation in a normally read only section of memory which cause the runtime linker to have to do the hussle to work around it. On ppc however the entire PT_LOAD is RWE so trying to fix this almost seems moot. PPC Team: (please explore these patches) http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01134.html http://sources.redhat.com/ml/binutils/2005-05/msg00391.html Steffen, You should also file a new bug for the undefined symbol problem in xineplug_decode_mpeg2.so. It's seperate from general textrels and probably a valid bug that should be fixed upstream. Hi solar, (In reply to comment #2) > Steffen, > You should also file a new bug for the undefined symbol problem in > xineplug_decode_mpeg2.so. It's seperate from general textrels and > probably a valid bug that should be fixed upstream. > what do you mean? Isn't the undefined symbol error the TEXTREL? Or are these two seperate things? I thought it's the same problem because both scanelf and kaffeine tell me about symbols/constants and the "undefined symbol: constants" error is gone if the textrel "constants" is gone (USE="-altivec")... So do you mean that I found two different bugs? Btw. the kaffeine error is the same with the current xine-lib-1.1.2_pre20060328-r7! thx, Steffen (In reply to comment #3) > what do you mean? Isn't the undefined symbol error the TEXTREL? > Or are these two seperate things? they're different things indeed. textrels are reported by emerge but that's only a warning. they cause failure only when you're running with a PaX kernel that has NOELFRELOCS enabled (hardened does it, i think), otherwise you won't see any problems at runtime either. > I thought it's the same problem because both > scanelf and kaffeine tell me about symbols/constants and the "undefined symbol: > constants" error is gone if the textrel "constants" is gone (USE="-altivec")... > > So do you mean that I found two different bugs? looks like ;-). why the textrel info is related to the missing symbol is a good question, my guess is that the code in question is written in ppc assembly and someone forgot to export symbols from it. Hi solar, (In reply to comment #4) > (In reply to comment #3) > > what do you mean? Isn't the undefined symbol error the TEXTREL? > > Or are these two seperate things? > > they're different things indeed. textrels are reported by emerge but that's > only a warning. they cause failure only when you're running with a PaX kernel > that has NOELFRELOCS enabled (hardened does it, i think), otherwise you won't > see any problems at runtime either. > > > I thought it's the same problem because both > > scanelf and kaffeine tell me about symbols/constants and the "undefined symbol: > > constants" error is gone if the textrel "constants" is gone (USE="-altivec")... > > > > So do you mean that I found two different bugs? > > looks like ;-). why the textrel info is related to the missing symbol is a good > question, my guess is that the code in question is written in ppc assembly > and someone forgot to export symbols from it. > here is the new bugreport for the missing symbol you wanted me to report: http://bugs.gentoo.org/show_bug.cgi?id=134745 Thanks, Steffen This is fixed together with bug #134745 in -r11. |