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

Conflicts:

	src/plugins/debugger/gdbengine.cpp

also, make it complain upon abuse of this call.

Conflicts:

	src/plugins/debugger/gdbengine.cpp

the inferior exited.
    Details:  that catches early exits due to startup problems as well

extra prompting

Conflicts:

	src/plugins/debugger/gdbengine.cpp

just treat it the same as internal apps as far as gdbengine is
concerned.

failed

    Details:  feels better

sometimes...

Conflicts:

	src/plugins/debugger/gdbengine.cpp

Conflicts:

	src/plugins/debugger/gdbengine.cpp

setting

initialization

watch view update

Conflicts:

	src/plugins/debugger/gdbengine.cpp

Conflicts:

	src/plugins/debugger/gdbengine.cpp

Conflicts:

	src/plugins/debugger/gdbengine.cpp

Conflicts:

	src/plugins/debugger/gdbengine.cpp

watch view update

values