- 10 Mar, 2009 2 commits
-
- 09 Mar, 2009 1 commit
-
-
hjk authored
Details: accounted for >60% startup time in some cases and was presumably only needed as help for a fallback when setting breakpoints with gdb 6.5 on Windows
-
- 05 Mar, 2009 2 commits
-
-
Oswald Buddenhagen authored
rely on the inferior's pid being available. consequently, remove the bizarre findChild stuff.
-
Oswald Buddenhagen authored
fixes interrupting processes with some versions of gdb
-
- 04 Mar, 2009 1 commit
-
-
hjk authored
-
- 03 Mar, 2009 2 commits
- 02 Mar, 2009 2 commits
- 27 Feb, 2009 1 commit
-
-
Oswald Buddenhagen authored
includes complete refactoring of ConsoleProcess.
-
- 25 Feb, 2009 2 commits
- 24 Feb, 2009 13 commits
-
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
- remove stale connect() - clear buffer after it was completely used
-
Oswald Buddenhagen authored
fixes chopping up of very long responses which quickly follow other responses. the line segmentation is done in readGdbStandardOutput() now. handleResponse() is not called through a queued slot any more, as the output receiver is already synchronized to the event loop.
-
Oswald Buddenhagen authored
it's broken and nobody seems to have noticed. that might be because the interpreter doesn't care whether something is a list or a tuple. if this is reintroduced for some reason, it should be done directly in the affected code path.
-
Oswald Buddenhagen authored
setting the initial breakpoint at the entry point wreaks havoc, so set it at main() instead. this will miss any breakpoints in global ctors and (currently) makes it impossible to set an actual breakpoint at main.
-
Oswald Buddenhagen authored
unlike the upstream gdb, the mac one gives an MI response to "info target" when in MI mode.
-
Oswald Buddenhagen authored
instead of picking "random" known entry point symbols, ask the debugger for the actual entry point. this also removes the "one instruction after the first one" hack, as it seems fairly pointless. NOTE: this does *not* work with the 2005 version of apple gdb. Conflicts: src/plugins/debugger/gdbengine.cpp
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
-
hjk authored
-
Oswald Buddenhagen authored
Conflicts: src/plugins/debugger/gdbengine.cpp
-
Oswald Buddenhagen authored
also, make it complain upon abuse of this call. Conflicts: src/plugins/debugger/gdbengine.cpp
-
Oswald Buddenhagen authored
-
- 23 Feb, 2009 2 commits
-
-
Oswald Buddenhagen authored
-
hjk authored
-
- 20 Feb, 2009 2 commits
-
-
Oswald Buddenhagen authored
instead of picking "random" known entry point symbols, ask the debugger for the actual entry point. this also removes the "one instruction after the first one" hack, as it seems fairly pointless. NOTE: this does *not* work with the 2005 version of apple gdb.
-
Oswald Buddenhagen authored
-
- 19 Feb, 2009 1 commit
-
-
hjk authored
-
- 18 Feb, 2009 4 commits
-
-
Marius Bugge Monsen authored
RevBy: ossi
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
also, make it complain upon abuse of this call.
-
Oswald Buddenhagen authored
-
- 17 Feb, 2009 5 commits
-
-
hjk authored
the inferior exited. Details: that catches early exits due to startup problems as well
-
Roberto Raggi authored
-
hjk authored
-
hjk authored
extra prompting
-
hjk authored
Conflicts: src/plugins/debugger/gdbengine.cpp
-