Dear all,
It seems that Android prebuilt arm-eabi-gdb will have problem to load
some shared library. arm-eabi-gdb will load the shared library to
wrong address, such as 0xfff?????. Then we can't set & trace the
breakpoints of these libraries.
We got the warning message like these:
.dynamic section for "libhardware.so" is not at the expected address
difference appears to be caused by prelink, adjusting expectations
After review the code of android toolchain, I remove some code in
android-toolchain-20081019/gdb-6.6/gdb/solib-svr4.c
/* If the changes match the alignment requirements, we
assume we're using a core file that was generated by the
same binary, just prelinked with a different base offset.
If it doesn't match, we may have a different binary, the
same binary with the dynamic table loaded at an unrelated
location, or anything, really. To avoid regressions,
don't adjust the base offset in the latter case, although
odds are that, if things really changed, debugging won't
quite work. */
#if 0
if ((l_addr & align) == 0 && ((dynaddr - l_dynaddr) & align) == 0)
{
l_addr = l_dynaddr - dynaddr;
warning (_(".dynamic section for \"%s\" "
"is not at the expected address"), so->so_name);
warning (_("difference appears to be caused by prelink, "
"adjusting expectations"));
}
else
#endif
warning (_(".dynamic section for \"%s\" "
"is not at the expected address "
"(wrong library or version mismatch?)"), so->so_name);
Then it can load sharedlibrary normally. But I'm not sure if it's
right solution to resolve this issue. So post these message. Anyone
can help?
Regards,
Jill
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
