Win64 doesn't seem to have raise() at all, or at least it isn't
called on abort()
Change-Id: Ief7a97c321db0f91629848852719977d14094173
Reviewed-by: hjk <qthjk@ovi.com>
'Remote connection closed' messages sometimes also arrive camuflaged
as a response to a command (with the response of the original
command already there).
Change-Id: I8fa75f561fb341463fc4c0ed0a35aa6fd8300694
Reviewed-by: hjk <qthjk@ovi.com>
This prevents initial reading of debug information when no
breakpoints are set. The debug information will be read on
first stop instead, e.g. when the user interrupts.
Change-Id: I6156347bf108e9ed89f54ca67021f37c02fa5116
Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com>
This also allows simple setting of breakpoints on failed asserts.
Change-Id: I6dd84cbfaf659d57e39f3447386cebc0221b2b84
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
This is yet another error that gdb 7.4 prints on windows when
the remote gets disconnected.
Change-Id: I7bc5f37bc9d9ae5211f23cf23dc19a8efd1779c8
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>
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>
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>
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>
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 47def926c7)
Change-Id: I18e8b77b615cfceec402b140337709074ad96dc5
Reviewed-by: hjk <qthjk@ovi.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>
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>
- 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>
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>
