*** Changes since GDB 6.8
+* GDB now has an interface for JIT compilation. Applications that
+dynamically generate code can create symbol files in memory and register
+them with GDB. For users, the feature should work transparently, and
+for JIT developers, the interface is documented in the GDB manual in the
+"JIT Compilation Interface" chapter.
+
* Tracepoints may now be conditional. The syntax is as for
breakpoints; either an "if" clause appended to the "trace" command,
or the "condition" command is available. GDB sends the condition to
with the `remote:' prefix, either via the `set sysroot' command or via
the `--with-sysroot' configure-time option.
+* "info sharedlibrary" now takes an optional regex of libraries to show,
+and it now reports if a shared library has no debugging information.
+
* Commands `set debug-file-directory', `set solib-search-path' and `set args'
now complete on file names.
macros.
* GDB now supports inspecting extra signal information, exported by
- the new $_siginfo convenience variable. The feature is currently
- implemented on linux ARM, i386 and amd64.
+the new $_siginfo convenience variable. The feature is currently
+implemented on linux ARM, i386 and amd64.
+
+* GDB can now display the VFP floating point registers and NEON vector
+registers on ARM targets. Both ARM GNU/Linux native GDB and gdbserver
+can provide these registers (requires Linux 2.6.30 or later). Remote
+and simulator targets may also provide them.
* New remote packets
visible changes; see "New commands" and also "Removed commands"
below.
+* Target descriptions can now describe the target OS ABI. See the
+"Target Description Format" section in the user manual for more
+information.
+
+* Target descriptions can now describe "compatible" architectures
+to indicate that the target can execute applications for a different
+architecture in addition to those for the main target architecture.
+See the "Target Description Format" section in the user manual for
+more information.
+
+* Multi-architecture debugging.
+
+ GDB now includes general supports for debugging applications on
+ hybrid systems that use more than one single processor architecture
+ at the same time. Each such hybrid architecture still requires
+ specific support to be added. The only hybrid architecture supported
+ in this version of GDB is the Cell Broadband Engine.
+
+* GDB now supports integrated debugging of Cell/B.E. applications that
+use both the PPU and SPU architectures. To enable support for hybrid
+Cell/B.E. debugging, you need to configure GDB to support both the
+powerpc-linux or powerpc64-linux and the spu-elf targets, using the
+--enable-targets configure option.
+
* New commands (for set/show, see "New options" below)
+catch syscall [NAME(S) | NUMBER(S)]
+ Catch system calls. Arguments, which should be names of system
+ calls or their numbers, mean catch only those syscalls. Without
+ arguments, every syscall will be caught. When the inferior issues
+ any of the specified syscalls, GDB will stop and announce the system
+ call, both when it is called and when its call returns. This
+ feature is currently available with a native GDB running on the
+ Linux Kernel, under the following architectures: x86, x86_64,
+ PowerPC and PowerPC64.
+
find [/size-char] [/max-count] start-address, end-address|+search-space-size,
val1 [, val2, ...]
Search memory for a sequence of bytes.
* New options
+set spu stop-on-load
+show spu stop-on-load
+ Control whether to stop for new SPE threads during Cell/B.E. debugging.
+
+set spu auto-flush-cache
+show spu auto-flush-cache
+ Control whether to automatically flush the software-managed cache
+ during Cell/B.E. debugging.
+
set sh calling-convention
show sh calling-convention
Control the calling convention used when calling SH target functions.
-set print symbol-loading
-show print symbol-loading
- Control printing of symbol loading messages.
-
set debug timestamp
show debug timestamp
Control display of timestamps with GDB debugging output.
Control use of remote protocol `qXfer:siginfo:write' (write-siginfo-object)
packet.
+set remote reverse-continue
+show remote reverse-continue
+ Control use of remote protocol 'bc' (reverse-continue) packet.
+
+set remote reverse-step
+show remote reverse-step
+ Control use of remote protocol 'bs' (reverse-step) packet.
+
set displaced-stepping
show displaced-stepping
Control displaced stepping mode. Displaced stepping is a way to
Allow GDB to resume all threads of all processes or only threads of
the current process.
+set stack-cache
+show stack-cache
+ Use more aggressive caching for accesses to the stack. This improves
+ performance of remote debugging (particularly backtraces) without
+ affecting correctness.
+
+set interactive-mode (on|off|auto)
+show interactive-mode
+ Control whether GDB runs in interactive mode (on) or not (off).
+ When in interactive mode, GDB waits for the user to answer all
+ queries. Otherwise, GDB does not wait and assumes the default
+ answer. When set to auto (the default), GDB determines which
+ mode to use based on the stdin settings.
+
* Removed commands
info forks
Lattice Mico32 lm32-*
x86 DICOS i[34567]86-*-dicos*
x86_64 DICOS x86_64-*-dicos*
+S+core 3 score-*-*
* The GDB remote stub, gdbserver, now supports x86 Windows CE
(mingw32ce) debugging.