I'm not sure what you want a screen shot of, or what it could possibly tell you.
Imagine I've got a library project called MYLIB and an executable project called MYAPP that uses MYLIB. In MYAPP's Project References page, I have MYLIB checked. When I select MYAPP, and click the hammer, it builds MYLIB first, then builds MYAPP. If I click the bug, it only builds MYAPP, so any changes made to MYLIB source don't get recompiled, and the final MYAPP executable has the old library code in it. Pretty simple. So to debug, I have to click the hammer and then the bug.
Of course, in the Debug perspective, there is no hammer button, so I have to go into the menu and do Project->Build Project first, and then click the bug to launch the program in the debugger. My reflex is just to click the bug, so often I forget. This is clearly not how it should work. If I click the bug, it should build MYLIB, build MYAPP, and then launch MYAPP.
I don't know if this is a bug specifically in the KDS IDE, or a general Eclipse bug, since I've never created and used my own library project in other Eclipse IDEs before.
