this is based on patches from axasia, which are in turn an almost
literal copy from qt.

includes complete refactoring of ConsoleProcess.

will use it also in the debugger, and pulling it in from projectexplorer
just seems wrong.

Details:  The non-continouous links were reported recently. All fixed now :)

RevBy: Will be looked at by Eike

Conflicts:
	src/plugins/coreplugin/editormanager/editorgroup.cpp
	src/plugins/coreplugin/editormanager/editorgroup.h
	src/plugins/coreplugin/editormanager/stackededitorgroup.cpp
	src/plugins/coreplugin/editormanager/stackededitorgroup.h
	src/plugins/qt4projectmanager/buildparserfactory.cpp
	src/plugins/qt4projectmanager/buildparserfactory.h
	src/plugins/qt4projectmanager/gccparser.h
	src/plugins/qt4projectmanager/gccpreprocessor.cpp
	src/plugins/qt4projectmanager/gccpreprocessor.h
	src/plugins/qt4projectmanager/headerpath.h
	src/plugins/qt4projectmanager/msvcenvironment.cpp
	src/plugins/qt4projectmanager/msvcenvironment.h
	src/plugins/qt4projectmanager/msvcparser.h

- remove stale connect()
- clear buffer after it was completely used

fixes chopping up of very long responses which quickly follow other
responses.

the line segmentation is done in readGdbStandardOutput() now.
handleResponse() is not called through a queued slot any more, as the
output receiver is already synchronized to the event loop.

it's broken and nobody seems to have noticed. that might be because the
interpreter doesn't care whether something is a list or a tuple.
if this is reintroduced for some reason, it should be done directly in
the affected code path.

Learn from this. ;)

Hasn't received a lot of testing, so will have to see whether this
works in practice.

Task:     - found by Denis
RevBy:    - Thomas
AutoTest: - manual
Details:  - we have some broken doc entrys, they won't return a url at all

Wasn't being patched up.

setting the initial breakpoint at the entry point wreaks havoc, so set
it at main() instead. this will miss any breakpoints in global ctors and
(currently) makes it impossible to set an actual breakpoint at main.

unlike the upstream gdb, the mac one gives an MI response to "info
target" when in MI mode.

Conflicts:
	src/plugins/debugger/debugger.pro
	src/plugins/debugger/gdbengine.cpp

instead of picking "random" known entry point symbols, ask the debugger
for the actual entry point.
this also removes the "one instruction after the first one" hack, as it
seems fairly pointless.
NOTE: this does *not* work with the 2005 version of apple gdb.

Conflicts:

	src/plugins/debugger/gdbengine.cpp