Arm Graphics Analyzer

Can any one help with the usage of Graphics Analyzer?

I have connected host and target using port 5002. Also, in the GA mobile application it is detecting my application as a traceable app. But not able to collect trace data on host.

These are the messages on Console:

[INFO]: Target event: CONNECTION_REQUEST, [com.arm.mgd.core.target.data.DeviceConnectionRequestEventAttachment@6a11c8af]
[INFO]: Target event: AUTHORISATION_REQUEST, [com.arm.mgd.core.target.data.FeatureAuthorisationRequestEventAttachment@60e9a3df]
[INFO]: Target event: DEVICE_INFO, [com.arm.mgd.core.target.data.DeviceInfoEventAttachment@48b65dfb]

Parents
  • Hi mgupt, 

    It sounds like you are running on Android. The Graphics Analyzer interceptor uses a local domain socket to connect the application being instrumented to the on-target daemon, which is used to package the data for the host machine. In recent versions of the Android SDK, applications are placed inside a more restrictive security sandbox which blocks access to the method we use to create the local domain socket.

    As a workaround for this issue, build the application being tested using a manifest that sets the targetSdkVersion to 25 or lower. We are working on a fix for the next release which should mean that this workaround is no longer required.

    If this doesn't help can you send us a logcat capture of your application (it's more likely that the error is thrown by the interceptor library not the daemon application).

    Kind regards, 
    Pete

Reply
  • Hi mgupt, 

    It sounds like you are running on Android. The Graphics Analyzer interceptor uses a local domain socket to connect the application being instrumented to the on-target daemon, which is used to package the data for the host machine. In recent versions of the Android SDK, applications are placed inside a more restrictive security sandbox which blocks access to the method we use to create the local domain socket.

    As a workaround for this issue, build the application being tested using a manifest that sets the targetSdkVersion to 25 or lower. We are working on a fix for the next release which should mean that this workaround is no longer required.

    If this doesn't help can you send us a logcat capture of your application (it's more likely that the error is thrown by the interceptor library not the daemon application).

    Kind regards, 
    Pete

Children
No data
More questions in this forum