Hi David, Ususally, adb logcat will show you the symbols that are missing. Are you seeing a case where it doesn't?
-joe On Thu, Mar 27, 2008 at 10:56 AM, David Given <[EMAIL PROTECTED]> wrote: > > We're doing some work involving JNI and a native library. (Yes, we are > aware that this is officially unsupported and that There Be Dragons Here.) > > If we try to load a library which has an unresolved symbol in it, > System.loadLibrary() throws an exception complaining that it can't find > the relevant library. That's all the information we get. > > Is there any way to find out *which* symbols could not be resolved and > which caused the library not to load? It would speed our debugging up no > end... > > -- > David Given > [EMAIL PROTECTED] > > > > --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
