On Wednesday, October 3, 2012 2:36:34 AM UTC-7, gjs wrote: > > Hi, > > "debug messages" was to imply anything emitted by locat, System.out.. , > System.err.. , printStackTrace from Exception etc > > And yes it's the same whether through Eclipse or otherwise, I suggested it > can be painful when debugging in Eclipse with some real (non Google > sponsored) devices that emit an excessive amount of these messages to find > your own messages within that mess, filtering and redirecting to file and > grep and changing buffer sizes and other time wasting [sic] steps aside. > Some of the carrier sourced devices fill the default Eclipse buffer in a > minute or so, particularly when GPS is on, the Google devices Galaxy S, > Galaxy Nexus, Nexus 7 don't. > >> As you say, the volume of output can be excessive, but if so, it's the same excess as in command line.
I don't believe the steps to filter output and adjust buffer sizes can be considered time wasting. Time is wasted if it produces less value than it costs. These steps produce more value than they cost. While I normally use only command line myself, I find the Eclipse logcat window to be very flexible. It has all sorts of convenient tools to help you filter your messages, so if anything folks would find it easier to use than command line, contrary to your conclusions. It lets you dynamically filter on debug level, process id (pid), regexes, app, tag or specific text. AFAICT it's infinite, so buffer size is a non-issue, and it has buttons to save the output and manage your filters. YMMV, but I don't recommend scaring people off the Eclipse logcat window. -- Lew -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
