最新国产好看的视频,伊人天堂AV在线,国产Aaaaaa视频,蜜臀视频在线观看一区,人妻av色图,密臀久久久精品影片,青青视频免费观看毛片,久草在线观看视,国产三级精品色情在线

在android中如何用Java加載解析so

 更新時(shí)間:2021年10月09日 11:20:45   作者:小道安全  
我們?cè)赼ndroid開(kāi)發(fā)項(xiàng)目過(guò)程中都必然會(huì)更so加載打交道,那么so加載在系統(tǒng)中的順序和流程是怎樣的,我們就有必要對(duì)這個(gè)加載過(guò)程進(jìn)行熟悉了解掌握

理論基礎(chǔ)

so的加載是一種解析式裝載,這與dex有一定區(qū)別,dex是先加載進(jìn)行優(yōu)化驗(yàn)證生成odex,再去解析odex文件,而so更像邊解析邊裝載,在加載過(guò)程中主要解析是load段。
下面主要是以java層的so加載進(jìn)行從源碼上進(jìn)行解析加載流程。

java層的so加載流程分析

 System.loadLibrary入口點(diǎn)

在java層我們知道加載so文件是通過(guò)System.loadLibrary函數(shù)其實(shí)現(xiàn)的,下面就以其作為入口點(diǎn)進(jìn)行分析它的調(diào)用關(guān)系和實(shí)現(xiàn)。
System.loadLibrary在的函數(shù)定義系統(tǒng)source\libcore\luni\src\main\java\java\lang\system.java的文件中。

下面是其函數(shù)定義實(shí)現(xiàn)。

//參數(shù)就是要加載的so文件名稱
 public static void loadLibrary(String libName) {
         //通過(guò)調(diào)用Runtime下面的loadLibrary函數(shù)實(shí)現(xiàn)
         //函數(shù)有兩個(gè)參數(shù),參數(shù)1是加載的so文件名,參數(shù)2 類加載器。
        Runtime.getRuntime().loadLibrary(libName, VMStack.getCallingClassLoader());
    }

Runtime的loadLibray解析

通過(guò)上面的System.java的loadLibrary函數(shù)我們需要繼續(xù)分析Runtime.java文件中的loadLibray函數(shù)的定義實(shí)現(xiàn)。
Runtime的loadLibrary函數(shù)在android系統(tǒng)中的位置是
source\libcore\luni\src\main\java\java\lang\Runtime.java文件。

下面是Runtime的 loadLibrary函數(shù)的定義實(shí)現(xiàn)源碼。

    /*
     * Searches for and loads the given shared library using the given ClassLoader.
     */
    void loadLibrary(String libraryName, ClassLoader loader) {
        if (loader != null) {
            //通過(guò)加載器去查找要加載的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;
        //循環(huán)遍歷文件路徑
        for (String directory : mLibPaths) {
            //文件路徑和文件名進(jìn)行拼接
            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解析

通過(guò)上面的Runtime的loadLibrary函數(shù),我們看到加載so的函數(shù)是走到doLoad函數(shù),那么我們就需要繼續(xù)分析Runtime下的doload函數(shù)的定義實(shí)現(xiàn)。
Rutime下的doload函數(shù)在系統(tǒng)中的
source\libcore\luni\src\main\java\java\lang\Runtime.java文件中。

下面的代碼是Runtime的doload函數(shù)的定義實(shí)現(xiàn)。

 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);
        }
    }

總結(jié)

從以上的源碼實(shí)現(xiàn)流程分析,我們可以看出Android在java層加載so的接口是System.loadLibrary(),通過(guò)層層遞進(jìn)關(guān)系從而實(shí)現(xiàn)java層的加載so。
下圖是詳細(xì)的java層加載so函數(shù)的調(diào)用關(guān)系。

在這里插入圖片描述

到此這篇關(guān)于在android中如何用Java加載解析so的文章就介紹到這了,更多相關(guān)Android 加載so內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!

相關(guān)文章

最新評(píng)論

永泰县| 香格里拉县| 施秉县| 安新县| 江川县| 武鸣县| 房山区| 崇州市| 黑山县| 平定县| 南康市| 九龙坡区| 荥经县| 娱乐| 于田县| 横山县| 吉木萨尔县| 安溪县| 南溪县| 雷州市| 晋宁县| 卢氏县| 平湖市| 报价| 通江县| 盱眙县| 天峻县| 昭觉县| 芜湖市| 寿阳县| 桐梓县| 淅川县| 灵台县| 丹巴县| 北票市| 高陵县| 隆安县| 呼和浩特市| 西乌珠穆沁旗| 临高县| 宽甸|