hjk
02f85a9949
debugger: adjust maemo adapter to new architecture
2010-07-14 17:49:17 +02:00
hjk
fa8cf20dc0
debugger: remove finished engines from snapshot list
2010-07-14 17:49:17 +02:00
hjk
4f4167a310
debugger: move BreakpointData into file of its own
2010-07-14 17:49:17 +02:00
hjk
99fdaf06a2
debuygger: make snapshots using true parallel engines
2010-07-14 17:49:17 +02:00
hjk
887e21da56
debugger: more state work
2010-07-14 17:49:17 +02:00
hjk
3eef8a43c0
debugger: more state work
2010-07-14 17:49:16 +02:00
hjk
cb68ec6656
debugger: adjust pdb engine to state machine changes
2010-07-14 17:49:16 +02:00
hjk
e760700f0f
debugger: overhaul "state machine"
...
This mainly allows for more precise shutdown and tightens the set
of allowed transitions.
2010-07-14 17:49:16 +02:00
hjk
6089bc1b9e
debugger: rename EngineStart to EngineSetup
2010-07-14 17:49:16 +02:00
hjk
9e7a456457
debugger: refactor startup logic
2010-07-14 17:49:16 +02:00
hjk
85243e19a9
debugger: encapsulate part of the startup logic in the base class
2010-07-14 17:49:15 +02:00
hjk
f8d96f09a6
debugger: rename startDebugger() to startEngine()
2010-07-08 13:48:09 +02:00
hjk
eab55aac6b
debugger: move state change to EngineStarting into the base class
2010-07-08 13:28:51 +02:00
hjk
2385e15b2d
debugger: merge 'AdapterStarting' into 'EngineStarting' state
2010-07-08 12:41:53 +02:00
hjk
cdf7dbeada
debugger: start refactoring of state transitions
...
This updates the state diagram in debuggerplugin.cpp and
renames AdapterStart{Fail}ed to EngineStart{Fail}ed.
2010-07-08 11:45:51 +02:00
hjk
038d943f9a
debugger: fix shutdown by pressing "[x]" in the output pane
2010-07-02 12:40:36 +02:00
hjk
200b18d44a
debugger: don't load registers if view is not shown
2010-06-28 10:30:18 +02:00
hjk
2bdf10ce10
debugger: reenable disabling of breakpoints in editor context menu
2010-06-25 17:38:25 +02:00
hjk
f3d38de913
debugger: fix breakpoint toggling of "moved" breakpoints
2010-06-25 17:38:25 +02:00
hjk
6493b4853d
debugger: adjust loading/saving of watched expressions to recent changes
2010-06-25 10:21:39 +02:00
hjk
ed2862acce
debugger: remove special mechanism to update watcher and return window
2010-06-23 14:12:14 +02:00
hjk
e6590ff598
debugger: fix addToWatchWindow
2010-06-23 11:06:01 +02:00
hjk
ccd46ec4cf
debugger: simplify debugger session data handling
2010-06-22 18:18:13 +02:00
hjk
817dbabd79
debugger: work on action handling
2010-06-22 17:46:44 +02:00
hjk
fadac8009c
debugger: more breakpoint management related fixes
2010-06-22 15:37:27 +02:00
hjk
c5c0dc76a0
debugger: restore session breakpoints if RunControl finishes
2010-06-22 15:14:44 +02:00
hjk
9a3acd48e4
debugger: re-connect 'executeDebuggerCommand'
2010-06-22 12:42:26 +02:00
hjk
f1cd284a33
debugger: connect some loose ends
2010-06-22 12:04:56 +02:00
hjk
6a6cba5518
debugger: The DebuggerEngine refactoring.
...
This replaces the (de facto) singleton engines and data handlers by classes
that are instantiated per run. The DebuggerRunControl will now create an
object of (a class derived from) DebuggerEngine that contains all the relevant
"dynamic" data.
DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin,
whereas the data bits went to DebuggerEngine.
There is no formal notion of a "current" DebuggerEngine. However, as there's
only one DebuggerEngine at a time that has its data models connected to the
view, there's still some "de facto" notion of a "current" engine. Calling
SomeModel::setData(int role, QVariant data) with custom role is used as the
primary dispatch mechanism from the views to the "current" data models
(and the engine, as all data models know their engine).
2010-06-22 10:59:57 +02:00
