Ok, seems like pointing to the null bytes fixes my issue :) yay Regards,
On Tue, Nov 2, 2010 at 4:13 PM, Rod Evans <[email protected]> wrote: > On 11/ 2/10 06:27 AM, Piotr Jasiukajtis wrote: >> >> Hi Rod, >> >> Thanks for explanation, however I don't understand why you writing >> offset 0xb4 while there is something at 0xd4 in the object. >> In fact the original libapr from the distribution (OpenSolaris) also >> has offset 0xd4 in the PT_SUNWCAP section. >> Is that a mistype? > > 0xb4 is the start of a string of nulls, and thus this "terminates" any > capabilities processing. I was under the suspicion that someone was > trying to remove any capabilities from the file. > > 0xd4 points at some data, but if this was interpreted as capabilities > it would seem invalid (at least for the file you sent me): > > ./libapr-0.so.0.9.17: warning: hardware capability (CA_SUNW_HW_2) \ > unsupported: 0x4 [ 0x4 ] > > So, what does "elfdump -H" reveal for the original libapr you have? > > BTW, we just integrated a fix for: > > 6996256 ld.so.1 capabilities checking should skip 0 sized section > > which allows your libapr to be loaded. > > -- > > Rod. > -- Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com _______________________________________________ tools-linking mailing list [email protected]
