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

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

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 - logcat overflow?

Hi all,maybe it is a stupid question... However when I see the logcat tab on the eclipse ddms perspective, when the logs are very verbose, happens that the logcat displays only one line each time. It refreshes the line but displays only one (So I can't read what happens in the line before because it disappears to show the next one).It seems that there is a limit in the number of lines that logcat window can contain and after that number the logcat switch to a single line mode...

Hi. It is not stupid question You need to configure your logcat for showing unlimited number of lines:I did it after configuring console. I really don't know why console configuration change logcat configuration.Go in Eclipse to Window->Preferences->Run/Debug->Console-> uncheck Limit Console output.

In my case your idea seems not to be functional. Is their anyone with a other idea? Because i need a longtime debug, my application going down after 5 or more hours. I don´t no really why, without a log i will have no chance to debug.

Quelle wrote:In my case your idea seems not to be functional. Is their anyone with a other idea? Because i need a longtime debug, my application going down after 5 or more hours. I don´t no really why, without a log i will have no chance to debug.

Thanks. Does Eclipse not automatically start adb?? In Eclipse i don´t see a way to enter a new console command. Now the Logcat commands are 9000 lines big, maybe it works correctly. I don`t know. If i start console with the adb command from outside eclipse, i don`t know how configure the console too save "endless" lines.

Is their any way too save the console commands realtime in a external file?

Quelle wrote:Thanks. Does Eclipse not automatically start adb?? In Eclipse i don´t see a way to enter a new console command. Now the Logcat commands are 9000 lines big, maybe it works correctly. I don`t know. If i start console with the adb command from outside eclipse, i don`t know how configure the console too save "endless" lines.

Is their any way too save the console commands realtime in a external file?

Regards florian.

I mean run this command outside of Eclipse.Yes, you can save output to the external file from your OS's system console.For example I use linux and in terminal I wrote

Quelle wrote:In my case your idea seems not to be functional. Is their anyone with a other idea? Because i need a longtime debug, my application going down after 5 or more hours. I don´t no really why, without a log i will have no chance to debug.

Quelle wrote:In my case your idea seems not to be functional. Is their anyone with a other idea? Because i need a longtime debug, my application going down after 5 or more hours. I don´t no really why, without a log i will have no chance to debug.

thanks and regard. quelle

I also use logcat in console. Just type in consoleadb logcat

How does one get timestamps on the log entries using this method?

This UNIX command sequence works for new log entries in real-time (old log entries are stamped with the same time stamps until the tail end of the logcat file is reached):