我刚把它修好了。在DDMS显示的最右边寻找恢复Devices Logcat视图和ADB视图的小图标。

When the DDMS first came up with both the "ADB Logs" and the "Devices | logcat" tab showing. The "Devices | logcat" is the one that should be showing the device output, but was blank. Somehow I managed to hide one or the other of those tabs, I forget exactly how. But, off to the right there was a tiny icon that said "Restore ADB" view, and I clicked it and it came up. Then there was another tiny icon that said "Restore Devices logcat view". I clicked that, and all of a sudden it appeared and was showing the device output again.

在“设备logcat”选项卡的右侧有一个按钮“只显示所选进程的logcat”。它并不完美，因为每次我运行另一个进程时，我都需要再次推动它，但这是唯一适合我的解决方案。到目前为止…

首先确保在您的设备中启用了开发人员选项。 设备已连接。 详细的。 只显示选中的应用程序。

在Android Studio 0.8.9中，我打开Android设备监视器，从设备列表中选择模拟器，并在LogCat选项卡中获得输出。

之后，我回到Android Studio的主视图，在Android DDMS选项卡的右侧选择Restore Logcat视图，它就在那里!

如果这不起作用，你可以在Android设备监视器中看到你的日志猫，就像我在第一句话中解释的那样。

所有这些都无济于事，我的日志猫功能失常。

After a lot of angry searching I found a solution that seems to work: 1. Make sure logcat itself is working (use DDMS from Tools->Android) and if it does close DDMS window again 2. Now go to Tab 5 (Debug), there select Logcat (this is not the same logcat as in Window 6!) 3. The window is empty just like Window 6, but now start a debugging run. For me logcat in the Debug window now started to show all the stuff again! Also when normally running the application the Debug->logcat view is still functional while the Tool Window #6 "logcat" is disfunctional as before

这是一个黑客，但是它会导致正常的logcat行为，突出显示您调试和开发所需的行和语法。 从现在开始，您需要通过调试窗口访问它。

Easy fix that worked for me (after trying some of these other suggestion). My logcat was sitting blank in a separate window (on my second screen). Just had to drag the Logcat tab back to it's original place in the debug panel next to the Debugger and Console tabs, and VOILA... it began immediately updating and showing all processes verbose. So (If your logcat is anywhere outside of the debugger panel (i.e. the logcat tab isn't sitting nested alongside the debugger and console tab) then it won't receive updates and will sit there blankly. Don't know if this is an issue with older versions of Android Studio. But again, easy to try and if it works... it works!!