纯净、安全、绿色的下载网站

首页|软件分类|下载排行|最新软件|IT学院

当前位置:首页IT学院IT技术

Android 加载so 在android中怎样用Java加载解析so

小道安全   2021-10-09 我要评论
想了解在android中怎样用Java加载解析so的相关内容吗小道安全在本文为您仔细讲解Android 加载so的相关知识和一些Code实例欢迎阅读和指正我们先划重点:Android,加载解析,so,Java,加载解析,so下面大家一起来学习吧

理论基础

so的加载是一种解析式装载这与dex有一定区别dex是先加载进行优化验证生成odex再去解析odex文件而so更像边解析边装载在加载过程中主要解析是load段
下面主要是以java层的so加载进行从源码上进行解析加载流程

java层的so加载流程分析

 System.loadLibrary入口点

在java层我们知道加载so文件是通过System.loadLibrary函数其实现的下面就以其作为入口点进行分析它的调用关系和实现
System.loadLibrary在的函数定义系统source\libcore\luni\src\main\java\java\lang\system.java的文件中

下面是其函数定义实现

//参数就是要加载的so文件名称
 public static void loadLibrary(String libName) {
         //通过调用Runtime下面的loadLibrary函数实现
         //函数有两个参数参数1是加载的so文件名参数2 类加载器
        Runtime.getRuntime().loadLibrary(libName, VMStack.getCallingClassLoader());
    }

Runtime的loadLibray解析

通过上面的System.java的loadLibrary函数我们需要继续分析Runtime.java文件中的loadLibray函数的定义实现
Runtime的loadLibrary函数在android系统中的位置是
source\libcore\luni\src\main\java\java\lang\Runtime.java文件

下面是Runtime的 loadLibrary函数的定义实现源码

    /*
     * Searches for and loads the given shared library using the given ClassLoader.
     */
    void loadLibrary(String libraryName, ClassLoader loader) {
        if (loader != null) {
            //通过加载器去查找要加载的so文件名
            String filename = loader.findLibrary(libraryName);
            //查找失败
            if (filename == null) {
                // It's not necessarily true that the ClassLoader used
                // System.mapLibraryName, but the default setup does, and it's
                // misleading to say we didn't find "libMyLibrary.so" when we
                // actually searched for "liblibMyLibrary.so.so".
                throw new UnsatisfiedLinkError(loader + " couldn't find \"" +
                                               System.mapLibraryName(libraryName) + "\"");
            }
            //加载so文件名
            String error = doLoad(filename, loader);
            if (error != null) {
                throw new UnsatisfiedLinkError(error);
            }
            return;
        }
        
        String filename = System.mapLibraryName(libraryName);
        List<String> candidates = new ArrayList<String>();
        String lastError = null;
        //循环遍历文件路径
        for (String directory : mLibPaths) {
            //文件路径和文件名进行拼接
            String candidate = directory + filename;
            candidates.add(candidate);

            if (IoUtils.canOpenReadOnly(candidate)) {
                String error = doLoad(candidate, loader);
                if (error == null) {
                    return; // We successfully loaded the library. Job done.
                }
                lastError = error;
            }
        }

        if (lastError != null) {
            throw new UnsatisfiedLinkError(lastError);
        }
        throw new UnsatisfiedLinkError("Library " + libraryName + " not found; tried " + candidates);
    }

Runtime的doLoad解析

通过上面的Runtime的loadLibrary函数我们看到加载so的函数是走到doLoad函数那么我们就需要继续分析Runtime下的doload函数的定义实现
Rutime下的doload函数在系统中的
source\libcore\luni\src\main\java\java\lang\Runtime.java文件中

下面的代码是Runtime的doload函数的定义实现

 private String doLoad(String name, ClassLoader loader) {
        // Android apps are forked from the zygote, so they can't have a custom LD_LIBRARY_PATH,
        // which means that by default an app's shared library directory isn't on LD_LIBRARY_PATH.

        // The PathClassLoader set up by frameworks/base knows the appropriate path, so we can load
        // libraries with no dependencies just fine, but an app that has multiple libraries that
        // depend on each other needed to load them in most-dependent-first order.

        // We added API to Android's dynamic linker so we can update the library path used for
        // the currently-running process. We pull the desired path out of the ClassLoader here
        // and pass it to nativeLoad so that it can call the private dynamic linker API.

        // We didn't just change frameworks/base to update the LD_LIBRARY_PATH once at the
        // beginning because multiple apks can run in the same process and third party code can
        // use its own BaseDexClassLoader.

        // We didn't just add a dlopen_with_custom_LD_LIBRARY_PATH call because we wanted any
        // dlopen(3) calls made from a .so's JNI_OnLoad to work too.

        // So, find out what the native library search path is for the ClassLoader in question...
        String ldLibraryPath = null;
        if (loader != null && loader instanceof BaseDexClassLoader) {
            ldLibraryPath = ((BaseDexClassLoader) loader).getLdLibraryPath();
        }
        // nativeLoad should be synchronized so there's only one LD_LIBRARY_PATH in use regardless
        // of how many ClassLoaders are in the system, but dalvik doesn't support synchronized
        // internal natives.
        synchronized (this) {
            return nativeLoad(name, loader, ldLibraryPath);
        }
    }

总结

从以上的源码实现流程分析我们可以看出Android在java层加载so的接口是System.loadLibrary()通过层层递进关系从而实现java层的加载so
下图是详细的java层加载so函数的调用关系

在这里插入图片描述


相关文章

猜您喜欢

  • 好用的Python技巧 分享13个好用到起飞的Python技巧

    想了解分享13个好用到起飞的Python技巧的相关内容吗程序猿-小菜在本文为您仔细讲解好用的Python技巧的相关知识和一些Code实例欢迎阅读和指正我们先划重点:python小技巧,python如何使用,python编程技巧下面大家一起来学习吧..
  • Android RecyclerView Android入门教程之RecyclerView的具体使用详解

    想了解Android入门教程之RecyclerView的具体使用详解的相关内容吗低吟不作语在本文为您仔细讲解Android RecyclerView的相关知识和一些Code实例欢迎阅读和指正我们先划重点:Android,RecyclerView,Android,入门下面大家一起来学习吧..

网友评论

Copyright 2020 www.fresh-weather.com 【世纪下载站】 版权所有 软件发布

声明:所有软件和文章来自软件开发商或者作者 如有异议 请与本站联系 点此查看联系方式