diff options
| -rw-r--r-- | gdb/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/NEWS | 30 |
2 files changed, 20 insertions, 15 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 1e2aa8d..4abc47d 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,10 @@ 2020-08-12 Pedro Alves <palves@redhat.com> + * NEWS: Move "Multi-target debugging support" item to the + "Changes since GDB 9" section. + +2020-08-12 Pedro Alves <palves@redhat.com> + PR gdb/26336 * progspace.c (program_space::remove_objfile): Invalidate the frame cache. @@ -25,6 +25,21 @@ You can get the latest version from https://sourceware.org/elfutils. +* Multi-target debugging support + + GDB now supports debugging multiple target connections + simultaneously. For example, you can now have each inferior + connected to different remote servers running in different machines, + or have one inferior debugging a local native process, an inferior + debugging a core dump, etc. + + This support is experimental and comes with some limitations -- you + can only resume multiple targets simultaneously if all targets + support non-stop mode, and all remote stubs or servers must support + the same set of remote protocol features exactly. See also "info + connections" and "add-inferior -no-connection" below, and "maint set + target-non-stop" in the user manual. + * New features in the GDB remote stub, GDBserver ** GDBserver is now supported on RISC-V GNU/Linux. @@ -212,21 +227,6 @@ BPF bpf-unknown-none This feature is still in testing, so it is disabled by default. You can turn it on using 'maint set worker-threads unlimited'. -* Multi-target debugging support - - GDB now supports debugging multiple target connections - simultaneously. For example, you can now have each inferior - connected to different remote servers running in different machines, - or have one inferior debugging a local native process, an inferior - debugging a core dump, etc. - - This support is experimental and comes with some limitations -- you - can only resume multiple targets simultaneously if all targets - support non-stop mode, and all remote stubs or servers must support - the same set of remote protocol features exactly. See also "info - connections" and "add-inferior -no-connection" below, and "maint set - target-non-stop" in the user manual. - * Python API ** The gdb.Value type has a new method 'format_string' which returns a |