Use a quint64 as address. Split apart special handling of
QAbstractItemModels of old shared-library based dumpers
(passing '$'+ special expression as address) into separate
dumperFlags QByteArray.

CDB: expand pointers correctly
Check for watchpoints at pointed to-addresses correctly.

Make address a quint64, linnumber and ignoreCounts int.

Reviewed-by: hjk

Task-number: QTCREATORBUG-982

Saves lots of conversion.

Finally.

http://bugreports.qt.nokia.com/browse/QTCREATORBUG-2126

http://bugreports.qt.nokia.com/browse/QTCREATORBUG-2144

items

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).

Change the WatchWindow handling to be based on quint64 addresses to
ensure proper function. Changed roles and added one role to the
watchmodel to obtain addresses and pointed-to addresses. Add some
fiddling to parse out addresses from debugger values.
Add menu options. Make sure only one watchpoint per address is added.

Works only with gdb/Python so far.

Reviewed-by: hjk

Task-number: QTCREATORBUG-1139

- Do not reformat boolean values (true,false) as hex/oct.
- char/unsigned char types (cdb/gdb): Chop off the quoted
  printable character output by the debugger, pass around integer
  only and append the character ourselves in the watchhandler,
  making reformatting as hex/octal work.
- cdb: Check format correctly (fix values output as plain integer).
- cdb: Kill needless warning produced by reformatting output of out-of-scope
  variables.
- cdb: Display exceptions in the status bar as non-intrusive crash notification.

Reviewed-by: hjk