Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4362: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4364: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4365: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4366: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)
anddev.org • View topic - ADB method profiling causes app to crash

ADB method profiling causes app to crash

Common bugs/problems with the Android SDK the Emulator and the ADT-Plugin.

ADB method profiling causes app to crash

Postby voullie » Mon Mar 05, 2012 10:56 am

Hi,

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?
voullie
Once Poster
Once Poster
 
Posts: 1
Joined: Mon Mar 05, 2012 10:46 am

Top

Return to SDK/ADT/Emulator Problems

Who is online

Users browsing this forum: Google [Bot] and 14 guests