I also experienced the same thing. Not only dlopen() but there may be many functions that will not be working. No documentation about those things yet. Really you will be wasting your time on using the C libraries in Android and experimenting using them. I recommend you to stay some time and continue native development when the documentation is available. I also tried really hard on few things and now waiting to see until some more information is available about the C library facilities available in Android.
Thanks, Diluka. David Given wrote: > David Given wrote: > [...] > >> I'm trying to use JNI to load a library. However, I seem to have a >> situation where System.loadLibrary() --- which I assume is calling >> dlopen() behind the scenes --- is incorrectly applying relocations in >> shared libraries. >> > [...] > > I'm sorry to keep hassling everyone, but does *anyone* know anything > about this? Even if it's as simple as, 'I agree, that looks odd, submit > a bug report' or 'We need more information, can you show us X, Y and Z'? > > Currently this is causing my app to be completely dead in the water: > we're using this construction heavily in the C side of things for tables > of function pointers, and right now it's calling all the wrong functions. > > I'm *hoping* that it's something simple I'm doing wrong in the link > phase, because then I can fix it pretty straightforwardly; but I can't > think what... > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" 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-internals?hl=en -~----------~----~----~----~------~----~------~--~---
