• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 136 subscribers
  • Views 5908 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Mali Graphics Debugger : application crash

chenwu

i want debug a game on Samsung GT-N7100 Galaxy Note II (gpu is Mali 400).


Mali Graphics Debugger version is 1.2.2.5b0519ce.


i run the Installation Instructions


adb shell su -c mount -o remount /system

adb push libGLES_mgd.so /sdcard/

adb push mgddaemon /sdcard/

adb shell

# The following commands run on the target

su

cd /sdcard/

cp mgddaemon /system/bin/mgddaemon

chmod 777 /system/bin/mgddaemon

cp libGLES_mgd.so /system/lib/egl/libGLES_mgd.so

chmod 777 /system/lib/egl/libGLES_mgd.so

cp /system/lib/egl/egl.cfg /system/lib/egl/egl.cfg.bak

echo "0 0 mgd" > /system/lib/egl/egl.cfg

but i found every application will crash.

if i revert the egl.cfg file,

cp /system/lib/egl/egl.cfg.bak /system/lib/egl/egl.cfg

every thing will be ok.

do i need some other config?

Could anyone help me on this problem?

Thank you in advance!

Parents
  • +1 Arm Employee Badge in reply to chenwu

    Hi chena, a couple of extra things to check...

    Can you let us know the output of adb logcat | grep EGL when egl.cfg is pointing at mgd, and you try and open the android settings application? please clear the log with adb logcat -c first and make sure the application is completely killed. This will show us what the fail looks like in logcat.

    Then can you do the following:

         adb shell

         su

         mount -o remount /system

         cd /system/lib/egl

         ln -s libGLES_mgd.so libEGL_mgd.so

         ln -s libGLES_mgd.so libGLESv2_mgd.so

         ln -s libGLES_mgd.so libGLESv1_CM_mgd.so

         chmod 777 *


    then please let us know the output of adb shell ls -l /system/lib/egl/, and then the output of adb logcat | grep EGL again following the same steps when you try and open settings? I just hit a similar problem on the S3 and it appears that frameworks/native/opengl/libs/EGL/Loader.cpp has been modified to ignore monolithic (libGLES_<tag>.so) drivers. This isn't a bug in MGD, but is a platform quirk introduced by the vendor that you can easily work around by adding the symlinks. With any luck it's the same problem you're facing and that will fix it for you.

    EDIT: We'll add these extra steps in a future version of MGD.

    Thanks,

    Chris

Reply
  • +1 Arm Employee Badge in reply to chenwu

    Hi chena, a couple of extra things to check...

    Can you let us know the output of adb logcat | grep EGL when egl.cfg is pointing at mgd, and you try and open the android settings application? please clear the log with adb logcat -c first and make sure the application is completely killed. This will show us what the fail looks like in logcat.

    Then can you do the following:

         adb shell

         su

         mount -o remount /system

         cd /system/lib/egl

         ln -s libGLES_mgd.so libEGL_mgd.so

         ln -s libGLES_mgd.so libGLESv2_mgd.so

         ln -s libGLES_mgd.so libGLESv1_CM_mgd.so

         chmod 777 *


    then please let us know the output of adb shell ls -l /system/lib/egl/, and then the output of adb logcat | grep EGL again following the same steps when you try and open settings? I just hit a similar problem on the S3 and it appears that frameworks/native/opengl/libs/EGL/Loader.cpp has been modified to ignore monolithic (libGLES_<tag>.so) drivers. This isn't a bug in MGD, but is a platform quirk introduced by the vendor that you can easily work around by adding the symlinks. With any luck it's the same problem you're facing and that will fix it for you.

    EDIT: We'll add these extra steps in a future version of MGD.

    Thanks,

    Chris

Children
No data