L
Lawrence D'Oliveiro
The Android documentation mentions the Log class
<http://developer.android.com/reference/android/util/Log.html> for use to
send messages to the system log (which you can view with the ‘adb logcatâ€
command). But this doesn’t seem to be necessary: I write messages to
System.err, and they appear in the log.
This
<http://developer.android.com/guide/developing/debugging/debugging-log.html>
says “By default, the Android system sends stdout and stderr (System.out and
System.err) output to /dev/null†and then proceeds to give a description of
how to change this default. I didn’t do this on my HTC, and yet I can see
stderr messages via logcat on that just fine.
Just as importantly, when my program crashes, the traceback appears in there
as well.
<http://developer.android.com/reference/android/util/Log.html> for use to
send messages to the system log (which you can view with the ‘adb logcatâ€
command). But this doesn’t seem to be necessary: I write messages to
System.err, and they appear in the log.
This
<http://developer.android.com/guide/developing/debugging/debugging-log.html>
says “By default, the Android system sends stdout and stderr (System.out and
System.err) output to /dev/null†and then proceeds to give a description of
how to change this default. I didn’t do this on my HTC, and yet I can see
stderr messages via logcat on that just fine.
Just as importantly, when my program crashes, the traceback appears in there
as well.