Android：DDMS 视角与调试视角
我注意到 Eclipse 中有两个调试视角是为 Android 开发设置的。
为什么是两个？
DDMS 透视图提供了哪些 Debug 透视图不提供的功能？
澄清一下，我只对 diff 类型的比较表感兴趣，而不是 DDMS 的完整功能列表。
我也很好奇为什么设计 DDMS 的人没有将其附加到调试透视图，而是选择将其实现为独立透视图。
（我在 DDMS 视角下，尝试通过放置断点来调试问题。当我运行程序时，Eclipse 要求我切换到 Debug 视角。这就是我问自己的点“为什么不将 DDMS 功能添加到调试透视图并避免切换？）
I noticed that there are two debug perspectives in Eclipse that is setup for Android development.
Why two?
What does the DDMS perspective provide that the Debug perspective doesn't provide?
To clarify, I am only interested in a diff kind of comparison table, not the full feature list of DDMS.
I am also curious to know why the folks who designed DDMS, didn't append it to the Debug perspective but rather chose to implement it as an independent perspective.
(I was on the DDMS perspective, trying to debug a problem by placing a breakpoint. When I ran the program, Eclipse asked me to switch to the Debug perspective. That was the point where I asked myself "why not add the DDMS functionality to the Debug perspective and avoid switching?)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
DDMS 允许您与模拟器进行交互，执行以下操作：
DDMS allows you to interact with the emulator doing things such as:
DDMS 透视图为您提供了调试透视图无法提供的大量信息。在 ddms 角度，您可以查看线程和每个线程使用的内存、每个应用程序的内存、查看应用程序和模拟器堆、分配跟踪器（在这里您可以步进异步任务，即）、logcat 比调试控制台要好得多，并且（对我来说）最重要的功能是方法分析，我可以在其中逐步跟踪我的应用程序执行的操作。
我忘记了模拟器动作模拟器，模拟呼叫，模拟位置，模拟短信等等......
DDMS perspective provides you a lot of information that debug perspective doesn´t. In ddms perspective you can wath Threads and the memory used for each thread, memory per application, see application and emulator heap, the allocation tracker (here you can step the asynchronous task i.e), the logcat are much more fine that debug console, and the most important function (to me) is the Method profiling, where i can follow step by step the actions performed by my application.
And i forgetting the emulator action simulator, simulate call, simulate locations, simulate sms, etc.etc...