Android: DDMS perspective vs. Debug perspective

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 开发者_如何学Cthe 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?)

---

DDMS allows you to interact with the emulator doing things such as:

• set location of phone, send gps coordinates, etc
• view the heap and track memory allocations
• profile methods and examine threads
• logcat
• spoof phone calls and sms messages

---

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...