UPDATE: This turned out to be a bug in R14 of the SDK tools. It has been fixed in R15 which was released on Oct. 27. Updating to the latest release solves the problem as suggested in the accepted answer.
I use the LogCat window in the Debug view in Eclipse to diagnose and fix crashes in my code. I've noticed that the LogCat output will automatically scroll down anytime new lines are added (but only after you scroll to the bottom yourself).
This is great if I'm waiting for an exception stacktrace to come up, but extremely annoying if I'm trying to read something in the log and more lines are continuing to be added at the bottom (it keeps jumping to the bottom, so I scroll back to the error, then it jumps to the bottom again).
Is there any way to make it stay where I've placed it, when I place it, but continue to scroll automatically when I reach the bottom?
EDIT: Please note, I'm aware of filters and I don't consider this a solution to the problem.
ANOTHER EDIT: If I scroll up "far enough" from the bottom, it stops scrolling automatically. Far enough might be 5 lines or it might be 500 lines, it seems to be related to how many lines are in the log. Ideally, it would stop scrolling as long as I was at least 1 line away from the bottom.
Source: Tips4all
update to the latest version. the new logcat automatically filters your logs into the app-specific crash logs when you build-launch your app via eclipse.
ReplyDeleteThat's not what happens to me. If I scroll up it won't scroll down automatically when new lines come to the logcat until I scroll it to the bottom.
ReplyDeleteMaybe it's because of the Eclipse or the Android SDK version. I'm using the latest right now.
You can do adb logcat in a shell, and use your terminal app's scroll buffer and scrolling features to manage the logcat output.
ReplyDeleteIn the LogCat tab on the upper far right there is a pause button to
ReplyDelete"Pause receiving new logcat messages"
That should do the trick!
If you're only debugging crashes, click on the red (E) (error) filter for your main logcat, and keep your filter tab set to default to view all lines that are being reported by your application.
ReplyDeleteWhat ends up happening, when your application crashes it stays closed unless requested to restart by your choosing. So, the last lines in the logcat will be the crash report. This is one of the ways of how I debug crashes.
I also think it is "more aggressive" since the latest update! And it actually stops auto-scrolling when I scroll 10 or more lines up.
ReplyDeleteThe best solution I have is clicking in the line you are interested in. If the logcat scrolls down too far and you don't see your line any more just press ArrowUp or ArrowDown to jump back to the line you were looking at.
Plop,
ReplyDeleteWindow=>Preferences=>Android=>Logcat
Unchecked the box:
"Display logcat view when there are messagesfro, an application into the workspace"
++
Giz