1055386 - Reactivate galaxy nexus profiling runs

Status: RESOLVED INCOMPLETE

(Testing Graveyard :: Eideticker, defect)

Description

[William Lachance (:wlach)]

We should get the galaxy nexus profiling runs working again with eideticker, they were useful.

Comment 1

[William Lachance (:wlach)]

When I try to use the profiler with recent builds, I'm getting this:

AndroidBrowserRunner INFO | Symbolicate: progress
AndroidBrowserRunner INFO | Symbolicate: progress
AndroidBrowserRunner INFO | Symbolicate: Resolving symbols for library /dev/ashmem/dalvik-jit-code-cache
AndroidBrowserRunner INFO | Symbolicate: /bin/bash -l -c 'arm-eabi-addr2line -C -f -e "/tmp/eideticker/tmp2AhXBJ/dalvik-jit-code-cache" 0x128 0x3b124 0x29628 0xae70 0x29bb8'
arm-eabi-addr2line: '/tmp/eideticker/tmp2AhXBJ/dalvik-jit-code-cache': No such file
AndroidBrowserRunner INFO | Symbolicate: progress
AndroidBrowserRunner INFO | Symbolicate: finished

A manual hack to readSymbolsLinux in the GeckoProfilerAddon's SymbolicateWorker.js to ignore dalvik-jit-code-cache works, but I wonder if there's a better solution here. BenWa?

Comment 2

[Benoit Girard (:BenWa)]

We might be able to get a flag for the code mapping that would identify it as a jit block, but given how rarely this comes up I don't think it's worth it.

Comment 3

[William Lachance (:wlach)]

Attachment: Hack around issue

I guess in that case I might as well ask for a review...