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>
gdb was not answering to "set breakpoint always-inserted on" at all.
Change-Id: I5fead2e735097236ba094d80bfbd4fa43143e5f7
Reviewed-by: hjk <qthjk@ovi.com>
This was for kernel i386 2.6.24-23-ubuntu and gdb 6.8.
This is pre-python, i.e. not supported anymore.
Change-Id: I1d73dbd6fd7730e15ebab334eb9d043b210eb631
Reviewed-by: hjk <qthjk@ovi.com>
This is expected to create more console output, which needs to be fixed
on a case-by-case base.
Change-Id: Ic83fb1d4c4392cfb421d9c2eba52b7bae705daae
Reviewed-by: hjk <qthjk@ovi.com>
If the user overrides a dumper function (e.g. threadnames), it is
not overridden when the target is a core dump, because the python
dumpers are re-read after loading the init scripts.
Change-Id: I8740228e754a4ed96352188bdfa4ffec95cdeaa0
Reviewed-by: hjk <qthjk@ovi.com>
This helps with MinGW on Linux.
Change-Id: I6495d0606738a8ad540477dcb820c62e0a06f34c
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
Reviewed-by: hjk <qthjk@ovi.com>
Make the second "Abort Debugger" kill the gdb process directly
instead of relying on further communication.
Also fix some "unexpected" (but harmless) state transitions.
Change-Id: I0938ec76420fbd77ec4b7348819dd7f63763547f
Reviewed-by: hjk <qthjk@ovi.com>
Removal of a breakpoint while the insertion result was pending worked,
but created a lot of noise about unexpected state transitions.
Change-Id: I6c101ee9d184efb1c44f72cbff99b0481f64b0eb
Reviewed-by: hjk <qthjk@ovi.com>
