it is alread used for the error cases anyway.
one could introduce an intermediate state InferiorRunningFailed, but
this doesn't seem to bring any advantages.
You now get the function parameters as a completion suggestion when
declaring or defining a function. The tooltip for function calls
is unchanged.
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
(cherry picked from commit 202fef42ca)
as it turns out, it is not possible to set pending breakpoints until
gdb has loaded as image. so add some hooks to enable adapters to trigger
the initial breakpoint syncing at the right time. do not add additional
states (say, InferiorPreparing), as it would just complicate things.
this includes:
- move the gdb ownership back to the engine (thus strip down the
adaptors as far as possible)
- make gdb startup synchronous
- make adapter shutdown synchronous
- fix the state transitions relating to shutdown
You now get the function parameters as a completion suggestion when
declaring or defining a function. The tooltip for function calls
is unchanged.
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
Includes Maemo tool chain, run configuration, run control,
manager, etc.
Adds the DebuggerManager to the object pool. This is ugly, but
nobody came up with anything better on short notice. To be
refactored.
Co-Authored-By: kh1
On UNIX, use SIGINT to interrupt the child, as the remote debugger's
-exec-interrupt does so as well.
On Windows, we get a SIGTRAP which we cannot influence.
As we currently do not know on which OS a remote debuggee is running,
accept either signal in that mode.
Reviewed-By: ossi
This should save debugger round trips and crashes in the debugging
helpers.
Add respective option to debugging helper option page, defaulting to
true.On this occasion, make CDB detect shadowed variables correctly
and display them as "<shadowed n>" as does the Gdb engine by
reversing the direction in which
CdbSymbolGroupContext::populateINameIndexMap works.
Rubber-stamped-by: hjk <qtc-committer@nokia.com>
