Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 139 subscribers
  • Views 17635 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Caught exception in initialiseRelocator: & not see tracing (Mali Debug)

Sergey

Hi

Such a problem, more precisely a few. I want to debug my own android game. I have two devices (armeadi-v7a, samsung tab s2 8.0 (Mali-T760, android 21) and Honor 7X(arm64-v8a, Mali-T830, android 26)  and I work with Mali Graphics Debugger (version 4.9.3 - host system OSX High Sierra 10.13.6). The problem is that on no one device working with debugging. Samsung : ( I launch as unrooted devices )  after I have done all the steps from User guide Mali debugger - When you run the application, you get the following error: 

E/libMGD: Tried to add symbol with same name: glEGLImageTargetTexture2DOES
Caught exception in initialiseRelocator: Tried to add symbol with same name: glEGLImageTargetTexture2DOES

And on this place stops loading. 

Honor : Everything is fixed, But, after the connection - it is there and on the idea should show on the screen - nothing happens. That is, I see a blank application screen Mali Graphics Debugger. 

That is, it does not work on any device. What is surprising. And yet, a year ago, everything worked for me owns samsung.   

  • 0 Arm Employee Badge

    Hi Sergey, 

    I've raised this with the MGD team, so hopefully we can shed some light on this.

    Cheers, 
    Pete

  • 0 in reply to Peter Harris

    Many thanks, I want you to know, for my part I am ready to render any possible help

  • 0

    I also encountered the same issue on Samsung SM-T280. Logs:


    08/03 12:13:44: Launching XXXXX
    $ adb install-multiple -r -t -p XXXXX
    Split APKs installed
    $ adb shell am start -n "XXXXX" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
    Client not ready yet..Connected to process 19040 on device sm_t280-31001b96218f3300
    Capturing and displaying logcat messages from application. This behavior can be disabled in the "Logcat output" section of the "Debugger" settings page.
    I/MultiDex: VM with version 2.1.0 has multidex support
    Installing application
    VM has multidex support, MultiDex support library is disabled.
    I/InstantRun: starting instant run server: is main process
    W/linker: libMGD.so: unused DT entry: type 0x6ffffffe arg 0x1d59c
    libMGD.so: unused DT entry: type 0x6fffffff arg 0x3
    I/libMGD: Initialising interceptor.
    Skipping line a2587000-a2ce6000 r-xp 00000000 b3:1b 66215 /XXXXX/lib/arm/libMGD.so
    Skipping line a2ce7000-a2d02000 r--p 0075f000 b3:1b 66215 /XXXXX/lib/arm/libMGD.so
    Skipping line a2d02000-a2d03000 rw-p 0077a000 b3:1b 66215 /XXXXX/lib/arm/libMGD.so
    Skipping line aa131000-aa241000 r-xp 00000000 b3:19 1303 /system/lib/egl/libGLES_mali.so
    Skipping line aa242000-aa245000 r--p 00110000 b3:19 1303 /system/lib/egl/libGLES_mali.so
    Skipping line aa245000-aa249000 rw-p 00113000 b3:19 1303 /system/lib/egl/libGLES_mali.so
    I/libMGD: Skipping line b6cc0000-b6d1d000 r-xp 00000000 b3:19 1339 /system/lib/libEGL.so
    Skipping line b6d1d000-b6d1f000 r--p 0005c000 b3:19 1339 /system/lib/libEGL.so
    Skipping line b6d1f000-b6d28000 rw-p 0005e000 b3:19 1339 /system/lib/libEGL.so
    I/libMGD: Parsing /data/dalvik-cache/arm/data@app@XXXXX@base.apk@classes.dex
    V/libMGD: Couldn't locate DT_JMPREL relocations table
    I/libMGD: Could not parse /data/dalvik-cache/arm/data@app@XXXXX@base.apk@classes.dex
    Parsing /system/bin/app_process32
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 1 symbol relocations in /system/bin/app_process32
    Parsing /system/bin/linker
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/bin/linker
    Parsing /system/framework/arm/boot.oat
    V/libMGD: Couldn't locate DT_JMPREL relocations table
    I/libMGD: Could not parse /system/framework/arm/boot.oat
    Parsing /system/lib/libAstcEnc.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libAstcEnc.so
    Parsing /system/lib/libETC1.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libETC1.so
    Parsing /system/lib/libGLES_trace.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libGLES_trace.so
    Parsing /system/lib/libGLESv1_CM.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 7 symbol relocations in /system/lib/libGLESv1_CM.so
    Parsing /system/lib/libGLESv2.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libGLESv2.so
    Parsing /system/lib/libLLVM.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 2 symbol relocations in /system/lib/libLLVM.so
    Parsing /system/lib/libRS.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 2 symbol relocations in /system/lib/libRS.so
    Parsing /system/lib/libRScpp.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 2 symbol relocations in /system/lib/libRScpp.so
    Parsing /system/lib/libSEF.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libSEF.so
    Parsing /system/lib/libSEF4MP4.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libSEF4MP4.so
    Parsing /system/lib/libandroid.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 0 symbol relocations in /system/lib/libandroid.so
    Parsing /system/lib/libandroid_runtime.so
    V/libMGD: Couldn't locate DT_RELA relocations table
    I/libMGD: Found 558 symbol relocations in /system/lib/libandroid_runtime.so
    E/libMGD: Tried to add symbol with same name: glEGLImageTargetTexture2DOES
    E/libMGD: Caught exception in initialiseRelocator: Tried to add symbol with same name: glEGLImageTargetTexture2DOES
    Application terminated.

  • 0 Arm Employee Badge

    Hello Serjey, sdjt,
    thank you for your bug report!

    > E/libMGD: Tried to add symbol with same name: glEGLImageTargetTexture2DOES
    > Caught exception in initialiseRelocator: Tried to add symbol with same name: glEGLImageTargetTexture2DOES
    >
    I was not able to reproduce it with the device at hand, but I will look for a Samsung Galaxy Tab as soon as possible.
    Meanwhile I looked at our source code and I may have spotted a regression introduced since 4.9.2.
    If my hypothesis is correct, Mali Graphics Debugger 4.9.0 (https://developer.arm.com/products/software-development-tools/graphics-development-tools/mali-graphics-debugger/downloads) will work.
    I will try my best to find and fix the bug by the upcoming patch release and I will keep you posted.


    > Honor : Everything is fixed, But, after the connection - it is there and on the idea should show on the screen - nothing happens.
    > That is, I see a blank application screen Mali Graphics Debugger. 
    >
    Could you share/attach the logcat output?
    It may shed some light on what is going on there.


    Alberto

  • +1 in reply to Alberto Cerato

    Hi Alberto

    Thank you for your help! 

    I installed the version  4.9.0 - And at me all has earned on the device samsung galaxy tab s2 8.0 ! (Its fine work )

    Honor7X - Also does not launch the application in Mali graphics Debugger (MGD version 4.9.0) Attach Logs:

    logcatHonor7X.txt