mirror/binutils-gdb
2
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2025-02-23 13:21:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

Move multi-target NEWS entry to GDB 10 features

Browse Source 
Simon noticed that I managed to put this in the "Changes in GDB 9"
section by mistake instead of in the "Changes since GDB 9" section
where it belongs.

gdb/ChangeLog:

	* NEWS: Move "Multi-target debugging support" item to the
	"Changes since GDB 9" section.
This commit is contained in:
Pedro Alves 2020-08-12 19:46:13 +01:00
parent 27c7b875bd
commit 7cf663a932
2 changed files with 20 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View File

@ -1,3 +1,8 @@
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

30
gdb/NEWS
View File

@ -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