Fixing various problems with breakpoints and opened files caused by CDB
returning lower-case file names.
Task-number: QTCREATORBUG-438
Reviewed-by: hjk <qtc-committer@nokia.com>
Acked-by: mariusSO <qt-info@nokia.com>

Task-number: QTCREATORBUG-438

Reviewed-by: hjk
Task-number: QTCREATORBUG-399

Check for correct state (InferiorStopped).

Convert CDB unsigned integer values should they appear in hex,
make format flexible.
Use int64 for reformatting integers to be able to accommodate
64 bit values on Windows 64. Add some more integer types.
Do not save decimal type formats. Add menu option to clear
individual formatting. Do not use map[] to query the type formats
(inserting 0 everywhere as a side effect).

Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Adapt to the output format "0x0000000`0046535C".
Reviewed-by: hjk <qtc-committer@nokia.com>

Reviewed-by: hjk <qtc-committer@nokia.com>

Reviewed-By: hjk

unavailable

Fails for system Qt on 10.6.

Reviewed-By: hjk <qtc-committer@nokia.com>

The problem is that the shlib events disturb bounded execution requests
and there is no way to recover from this - the debugger will effectively
turn "step over" into "continue". this is nicely explained in
http://vladimir_prus.blogspot.com/2007/12/debugger-stories-pending-breakpoints.html

this ensures that, among other things, we won't get into this scenario:
- process is running
- interrupt is requested by user
- termination is requested by user
- before interrupt takes effect, the process terminates
=> shutdown is called
=> exit is also queued, as there is already a queued kill
=> nothing happens, as there will never be a stop response

Reviewed-by: hjk

archer reports stops at tbreaks properly, so checking for an empty stop
reason is no particularly good idea. instead, we simply skip *all* stops
at the entry point, assuming the user will not really set a breakpoint
there anyway.

Reviewed-by: hjk

When setting CDB_PATH via the environment.

Reviewed-By: ossi
(cherry picked from commit e288c4c4)

this is to update breakpoint, source and module lists automatically.

also remove the now pointless -break-list on every stop.

Reviewed-by: hjk

any output will most definitely belong to later issued commands, so not
clearing it will only cost cpu or even confuse the evaluation.

Reviewed-by: hjk

Reviewed-by: hjk

Reviewed-by: hjk

Use debugger's 'gu' command instead of temporary breakpoint as a
workaround until it is properly supported by the
SetExecutionStatus() API.

Reviewed-by: hjk
Task-number: QTCREATORBUG-240

Reviewed-by: hjk

That fix was correct.
This reverts commit 239e0418.

Reviewed-by: dt

The real problems is somewhere in the watch model. This patch does
only prevent the wrong (and unneeded) questions to be asked in the first
place. It does not fix the wrong handling of the answer in the watch model.

Reviewed-by: Oswald Buddenhagen

Reviewed-by: hjk <qtc-committer@nokia.com>
Reviewed-by: dt <qtc-committer@nokia.com>

Reviewed-by: dt

InferiorUnrunnable is equivalent to InferiorStopped as far as NeedsStop
commands are concerned.

Reviewed-by: hjk

sometimes, commands simply don't return ...

the debug message doesn't say anything which couldn't be found in the
log already, but that way it is more convenient.

and we kill gdb to get creator back to a defined state.

Reviewed-by: hjk

Reviewed-by: hjk <qtc-committer@nokia.com>

Reviewed-by: hjk <qtc-committer@nokia.com>