Change-Id: I2ea81b1a9407ae7e5045aadf43b0c2d971fc615b
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I92f47982067b57ca3d34a66977c557325d31ba09
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I6f80047ad229e0be851b06a277ab2f899757828f
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I78a22b885217ed45c97b992e0d70ef3bc19d24f9
Reviewed-by: hjk <qthjk@ovi.com>

Sometimes the "Remote connection closed" message is the last
one we get from gdbserver. handleResultRecord might not be called
any more.

Change-Id: Ib4c1155bf21c605ac39d75582c1a26676475cb7a
Reviewed-by: hjk <qthjk@ovi.com>

Task-number: QTCREATORBUG-7144
Change-Id: I204062de55e241ea7954f0e3bce123973028e076
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I335ce9427f4c7abea84e109323869226c07e7f7c
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

Task-number: QTCREATORBUG-6951
Change-Id: I35152a6f0422d4cbca356dab8b95033b166115fb
Reviewed-by: hjk <qthjk@ovi.com>

This seems to be the only way to make the setup work on Windows at all.

Change-Id: Ib70c8422dceea84ae5cc9e671de977de0887c80e
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I02219e496faa8918439467f72b196bf454b6bc8f
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I0bf982b508a237e5b1e6ba3279cb589bae1b1c1d
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

When terminating from within Qt Creator, we sometimes get a 'Quit'
message instead of 'Remote connection closed'.

Change-Id: I821d436813f1feacfe94ce85bc2175e3646dba27
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Id353ab140a46e06ffc3abf667ab3b234e749e17c
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

Following the  Change-Id: I18e8b77b615cfceec402b140337709074ad96dc5, I have
found the same behaviour in handleExecuteNext and HandleExecuteStep than in
hanleExecuteContinue. The fix is the same, If you click one of the two
buttons while having a different thread selected, notify the GUI of the gdb
error message but do not kill the debugger neither the inferior as the situation
can be addressed by clicking again step or next after switching to the
stopped thread.

Change-Id: I9f2951ea9846621156ceb3998514d7667d59e7af
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ibd7c9cafd4b16278e1db19155b285dd0ad2436cc
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I9063f4eecfe4c42926771cc46539932b4e353b8d
Reviewed-by: hjk <qthjk@ovi.com>

Make sure notifyInferiorExited is called when we get a
'Remote connection closed' message.

Change-Id: I578d62e29ed30243eb7693e641ad809cccd0fcae
Reviewed-by: hjk <qthjk@ovi.com>

When you hit a brekpoint in gdb non-stop mode, if you click continue in the
UI the debugger was killed if the current thread is not the one being
stopped. This is anoying as gdb does not change current thread
automatically. The fix shows the error but does not kill the inferior.
Fixed style issues again.

Reviewed-by: hjk <qthjk@ovi.com>
(cherry picked from commit 47def926)

Change-Id: I18e8b77b615cfceec402b140337709074ad96dc5
Reviewed-by: hjk <qthjk@ovi.com>

When you hit a brekpoint in gdb non-stop mode, if you click continue in the
UI the debugger was killed if the current thread is not the one being
stopped. This is anoying as gdb does not change current thread
automatically. The fix shows the error but does not kill the inferior.
Fixed style issues again.

Change-Id: I1a2e484108e936581c7b82c985f2b057263e3d6b
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ia24322bfecf8422cb5daec7b4fa4111bc36c00e8
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: If1d5bdd5afd2aeebfcf39e72045ef4327cb84c0c
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

Change-Id: I9e1751e890c42cc9f2d7f855b25c3d7e24b5501f
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I1882f1a49cca84456e9f94e608308d2c571fed67
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>

And adapt the other API respectively.

Change-Id: I1e04e555409be09242db6890f9e013396f83aeed
Reviewed-by: Bill King <bill.king@nokia.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

Change-Id: I0c8ba3c2d22ca7128527da42b81919dabbd82d14
Reviewed-by: hjk <qthjk@ovi.com>

By source - latin1 is really expected as there is no any check
or usage of QTextCodec::setCodecForCStrings() currently.

QString::fromAscii() might break 'Latin1' input in some cases.

A quote from documentation about QString::fromAscii():

"Note that, despite the name, this function actually uses the
codec defined by QTextCodec::setCodecForCStrings() to convert str
to Unicode. Depending on the codec, it may not accept valid
US-ASCII (ANSI X3.4-1986) input. If no codec has been set, this
function does the same as fromLatin1()."

Change-Id: I49cf047ca674d2ec621b517c635d1927bb2e796f
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>
Reviewed-by: hjk <qthjk@ovi.com>

Getting the #include directives ready for Qt5. This includes the
new-project wizards.

Change-Id: Ia9261f1e8faec06b9285b694d2b7e9a095978d2b
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

Change-Id: Ibf62cd0812eb113bec1ff49dec6d0017f57ccabf
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ifb2a378cdc000eb84b65f25c2132783d3a3f53c4
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I938affc8768c98aabcbde0250f8042cc6bf4a59e
Reviewed-by: hjk <qthjk@ovi.com>

Task-number: QTCREATORBUG-6893
Change-Id: Idb780e97c23f6cc5d1bcede149959b2e58f9eaa2
Reviewed-by: hjk <qthjk@ovi.com>

Task-number: QTCREATORBUG-6763
Change-Id: I7a95bdbb9ab7b85beb19b7d390a10a5d629dc7e7
Reviewed-by: hjk <qthjk@ovi.com>

- Windows: Always use DebugBreakProcess if Qt Creator is compiled
  64bit. Else always use win64interrupt.exe if Qt Creator
  is a WOW64 application.
- Remove redundant code (procinterrupt/hostutils, gdb adapters).
- Give interruptProcess an errorMessage parameter such that it can
  be used by all C++ engines and a proper error is displayed.
- Improve error messages.
- Build win64interrupt if target architecture is 64 bit (clean tools
  profile, add a profile), borrowing the check from
  qtcreatorcdbext.pro.

Change-Id: I2a6caf98e46051c49c84e1f3aac4c8d2aba66e8b
Reviewed-by: David Schulz <david.schulz@nokia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

Task-number: QTCREATORBUG-6773
Change-Id: I082b7d04730a5014ad935d6a079a1829dfcdd34c
Reviewed-by: hjk <qthjk@ovi.com>

- Add "Disassemble function..." action with dialog for name
  to stack window.
- Add "Disassemble" with function name from code model to
  the Editor context menu.
- Change the engines to be able to disassemble a function without
  address.

Change-Id: I812f4672d97d9a866ee7f5a38dbd18b2876bccfa
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I2ff075bcc5607fec9bd9dc8596108ec5f076d48d
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I62be12e5afe6d2b9a81c03e980e01a49dc4e4632
Reviewed-by: hjk <qthjk@ovi.com>

Just emit the requestRemoteSetup on your own in QmlCppEngine. Also
properly check the related state transitions in DebuggerEngine.

Change-Id: I15dc4236303911126de7eee63ed996bdd8e5c5a8
Reviewed-by: hjk <qthjk@ovi.com>

gdb was not answering to "set breakpoint always-inserted on" at all.

Change-Id: I5fead2e735097236ba094d80bfbd4fa43143e5f7
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ifc258886f7d6e7d5b02caae8994210aeef221554
Reviewed-by: Robert Löhning <robert.loehning@nokia.com>