On Feb 17, 6:30 pm, forest <[email protected]> wrote: > logcat -r 8000 -f /data/log.txt > can record all log,Freepine,thank you very much, > > hi,Sean McNeil,thank you too, > ++c; > LOGI(...); > has no effect
I verified that the LOG macro only refers to the arguments once, which is what I'd expect from __VA_ARGS__. However, this is not something that should be relied upon. The log mechanism doesn't drop messages, but if you write to the log faster than logcat can read you will possibly lose entries as the 64KB buffer wraps around. The problem will be exacerbated if the process doing the logging is beating the CPU senseless and not allowing logcat to run. Things get even more touchy if you're viewing logcat over adb, since you add the USB traffic through the adb server in there as well. If you have high-volume logging needs from native code you may want to open your own log file on /sdcard and just write to that instead of flooding the log device. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
