I'm developing an app that displays very high CPU usage, causing the battery to run out very quickly. To more accurately pinpoint what consumes all that CPU I decided to use the ADB method profiling feature. Starting method profiling causes my app to crash however. I have tried to start method profiling both through Eclipse->DDMS and the command line, both with the same result. The only message I get from LogCat is "Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)". I have tried starting method profiling several times and only once did I get a more verbose error message complaining about the Google Maps Service (my app uses the Google Maps API). I haven't been able to reproduce this message though which is why I cant post it here.
I'm developing for Android Google API 14 in Eclipse running on Mac OS X. I'm debugging on a Samsung Galaxy Nexus with Android version 4.0.2. Has anyone run into this problem or knows how to fix it?