Keep track of elf section headers, add a dumper for
Utils::ElfSection etc.
Change-Id: I06d01c0de01ffc6b827a4a79bdc91fdb3e761d75
Reviewed-by: hjk <qthjk@ovi.com>
It's one model for all locals, watch, return, tooltip and inspector
data. This allows more streamlined code paths and better isolation
of the model data from the WatchHandler. WatchItems are now registered
in a hash indexed by iname, so inames can be used as the primary
handle to watch data in the WatchHandler interface.
Change-Id: Idac0a808b5d785307496d1de4198a1f2e9ce3880
Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com>
Now the debug-file-location will not be replaced, but enhanced when new debug-file-locations are defined.
Change-Id: Ibabcd5814f281e5e378b29abcee1ac646b01cdcd
Reviewed-by: hjk <qthjk@ovi.com>
This reverts commit 89cee4313c,
as part of the patch breaks QTCREATORBUG-7277.
The GDB case should not filter the Locals model, but the Tooltip model
to display tooltips. CDB has no choice, as the tooltips are expressions,
i.e. cannot be handled, so using the Locals as fall back there is ok.
Change-Id: I196bc683e06f68301bd86aa6fcce14ad2e8c5774
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>
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>
