>>18
This is the right answer. I strongly dislike the amount of information that an IDE (like VS) hides from me, but it is worth the sacrifice to get the visibility that the debugger provides. You could probably piece together some custom tools and get something close to the streamlined-ness of VS, but why bother?
I will stick with VS until there's something different that provides this level of convenience:
1) Type some code.
2) Set a breakpoint at an line of source.
3) Press a key to compile/link/run it.
4) Code stops at set breakpoint.
5) Immediate visibility into all local variables, call stack, registers, memory contents, disassembly... plus single keystrokes for single stepping, "step over," "run to cursor," etc...
Yeah, all those functions are available in GDB or your favorite command-line debugger, but as
>>18-san said, the bottleneck in development is the time consumed in doing exactly these things (unless you're writing toy code).