All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Could not be committed due to merge conflict:
devel/py-traitlets/distinfo
The following distfiles were unfetchable (note: some may be only fetched
conditionally):
./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
This patch originates from pkgsrc-wip in order to prevent clang
warnings for adding an integer to a string literal by converting
"foo" + x to &"foo"[x]. However, when gdb was updated to 7.9, the
ampersand was mistakenly dropped. The string literal was also
replaced with a variable, so there is no longer any reason for the
patch.
This caused the oappend function to be called with a char converted
to a pointer, which immediately crashes gdb whenever disassembly
is performed.
October 24th, 2020: GDB 10.1 Released!
The latest version of GDB, version 10.1, is available for download.
This version of GDB includes the following changes and enhancements:
Support for debugging new targets:
BPF (bpf-unknown-none)
GDBserver support for the following targets:
ARC GNU/Linux
RISC-V GNU/Linux
Multi-target debugging support (experimental)
Support for debuginfod, an HTTP server for distributing ELF/DWARF debugging information as well as source code.
Support for debugging a 32-bit Windows program using a 64-bit Windows GDB.
Support for building GDB with GNU Guile 3.0 and 2.2 (in addition to 2.0)
Improved performance during startup through the use of threading during symbol table loading (an optional feature in GDB 9, now enabled by default in GDB 10).
Various enhancements to the Python and Guile APIs
Various TUI Mode fixes and enhancements.
Other miscellaneous enhancements:
Detection when attaching to a process of a mismatch between this process and the executable previously loaded into GDB.
Support for default arguments for "alias" commands.
GDBserver support for the following host triplets has been removed:
i[34567]86-*-lynxos*
powerpc-*-lynxos*
i[34567]86-*-nto*
bfin-*-*linux*
crisv32-*-linux*
cris-*-linux*
m32r*-*-linux*
tilegx-*-linux*
arm*-*-mingw32ce*
i[34567]86-*-mingw32ce*
See the NEWS file for a more complete and detailed list of what this release includes.
---
From: Joel Brobecker
Subject: GDB 9.1 released!
Date: Sat, 8 Feb 2020 18:56:59 +0400 (+04)
GDB 9.1 includes the following changes and enhancements:
* Building GDB and GDBserver now requires GNU make >= 3.82.
* If you choose to build GDB without using the GNU readline version bundled
with the GDB sources, building GDB new requires GNU readline >= 7.0.
* Removed targets and native configurations:
- GDB no longer supports debugging the Cell Broadband Engine;
- GDB no longer supports Solaris 10.
* New TI PRU Simulator (pru-*-elf).
* Python Enhancements:
- GDB can now be compiled with Python 3 on Windows;
- Various Python API enhancements;
* Usability enhancements:
- [experimental] Multithreaded symbol loading for higher performance
(turned off by default, use 'maint set worker-threads unlimited'
to turn this feature on);
- Command names can now use the '.' character;
- GDB can now place breakpoints on nested functions and subroutines
in Fortran;
- GDB now shows the Ada task names at more places, e.g. in task switching
messages.
- Styling enhancements to various commands to improve readability.
- GDB now has a standard infrastructure to support dash-style command
options ('-OPT'). One benefit is that commands that use it can
easily support completion of command line arguments. Try "CMD
-[TAB]" or "help CMD" to find options supported by a command. Over
time, we intend to migrate most commands to this infrastructure.
* Enhancements to existing commands:
- "printf" and "eval" can now print C-style and Ada-style strings
without calling functions in the program;
- "info sources" has been enhance to allow only printing files
whose name match a REGEXP;
- New value "presence" for the "set print frame-arguments" setting,
to only indicate the presence of arguments with '...' instead
of printing the argument names and values;
- The "focus", "winheight", "+", "-", ">", "<" TUI commands are
now case sensitive;
- New options support for the following commands that allow overriding
a number of relevant global settings (as set by e.g. "set print
[...]" commands): "print", "compile print", "backtrace", "frame
apply", "tfaas", "faas";
- "info types" support for "-q" to disable printing of some header
information;
- In settings, "unlimited" can now be abbreviated with "u".
* New commands:
- "define-prefix" to define user-defined prefix commands;
- "|" or "pipe" to execute a command and send its output to
a shell command.
- "with" to run a given command with a setting temporarily changed
to a given value;
- "set may-call-functions" to control whether subprogram can be
called from GDB;
- "set print finish [on|off]" to control whether the returned value
should be printed when using the "finish" command;
- "set print max-depth" to simplify the printing of deeply nested
structures;
- "set print raw-values [on|off]" to turn on and off pretty printers;
- "set logging debugredirect [on|off]" to control whether to redirect
debug output to the log file;
- Various new "set style" commands;
- "set print frame-info [...]" to control what information to print
when printing a frame.
- "set tui compact-source" to enable the "compact" mode for the TUI
source window;
- "info modules [...]" to query information about Fortran modules;
- The "set/show print raw-frame-arguments" commands replace
the "set/show print raw frame-arguments" (now with a dash instead of
a space). The latter is now deprecated and may be removed in
a future release.
* New GDB/MI commands
- "-complete" to list possible completions;
- "-catch-throw", "-catch-rethrow", and "-catch-catch", the GDB/MI
equivalent of the "catch throw", "catch rethrow", and "catch catch"
commands (respectively);
- "-symbol-info-functions", "-symbol-info-types", and
"-symbol-info-variables", the GDB/MI equivalent of the "info functions",
"info types", and "info variables" commands (respectively);
- "-symbol-info-modules", "-symbol-info-module-functions",
and "-symbol-info-module-variables", the GDB/MI equivalent of
"info modules", "info module functions" and "info module variables".
* Other MI changes
- The default version of the MI interpreter is now 3 (-i=mi3);
- The output of information about multi-location breakpoints (which is
syntactically incorrect in MI 2) has changed in MI 3;
- Backtraces and frames include a new optional field "addr_flags".
* Several new builtin convenience variables
- $_gdb_major and $_gdb_minor;
- $_gdb_setting, $_gdb_setting_str, $_gdb_maint_setting and
$_gdb_maint_setting_str
- $_cimag and $_creal
- $_shell_exitcode and $_shell_exitsignal
* Miscellaneous enhancements:
- Support for a new configure option "--with-system-gdbinit-dir",
where system gdbinit files are to be loaded from at startup;
- 'thread-exited' event is now available in the annotations interface;
- The TUI SingleKey keymap is now named "SingleKey" (requires
GNU readline >= 8.0).
For a complete list and more details on each item, please see the gdb/NEWS
file, available at:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-9.1-release
September 20th, 2019: GDB 8.3.1 Released!
This is a minor corrective release over GDB 8.3, fixing the following
issues:
* 20020 (GDB segfault on printing objects)
* 24454 (nat/x86-linux-dregs.c:146: internal-error: void
x86_linux_update_debug_registers(lwp_info*): Assertion `lwp_is_stopped
(lwp)' failed)
* 24541 (Incorrect evaluation of systemtap probes due to
register being signed and probe expression assuming unsigned)
* 24545 (Symbol loading performance regression with cc1)
* 24592 (amd64->i386 linux syscall restart problem)
* 25009 (terminate called after throwing an instance of
'srchilite::ParserException')
* 25010 (Calls to error () can cause SIGTTOU to send gdb to the
background)
* 25011 (Breakpoints on file reloads broken for PIE
binaries)
This corrective release also brings the following testsuite fixes and
enhancements:
* 25005 (gdb-caching-proc.exp takes a lot of time on
skip_opencl_tests)
* 25016 (Test-case failures for -pie)
May 11th, 2019: GDB 8.3 Released!
This version of GDB includes the following changes and enhancements:
* Support for new native configurations (also available as a target
configuration):
- RISC-V GNU/Linux (riscv*-*-linux*)
- RISC-V FreeBSD (riscv*-*-freebsd*)
* Support for new target configurations:
- CSKY ELF (csky*-*-elf)
- CSKY GNU/Linux (csky*-*-linux)
- NXP S12Z ELF (s12z-*-elf)
- OpenRISC GNU/Linux (or1k*-*-linux*)
* Native Windows debugging is only supported on Windows XP or later.
* The Python API in GDB now requires Python 2.6 or later.
* GDB now supports terminal styling for the CLI and TUI. Source
highlighting is also supported by building GDB with GNU Highlight.
* Experimental support for compilation and injection of C++ source code
into the inferior (requires GCC 7.1 or higher, built with libcp1.so).
* GDB and GDBserver now support IPv6 connections.
* Target description support on RISC-V targets.
* Various enhancements to several commands:
- "frame", "select-frame" and "info frame" commands
- "info functions", "info types", "info variables"
- "info thread"
- "info proc"
- System call alias catchpoint support on FreeBSD
- "target remote" support for Unix Domain sockets.
* Support for displaying all files opened by a process
* DWARF index cache: GDB can now automatically save indices of DWARF
symbols on disk to speed up further loading of the same binaries.
* Various GDB/MI enhancements.
* GDBserver on PowerPC GNU/Linux now supports access to the PPR, DSCR,
TAR, EBB/PMU, and HTM registers.
* Ada task switching support when debugging programs built with the
Ravenscar profile added to aarch64-elf.
* GDB in batch mode now exits with status 1 if the last executed command
failed.
* Support for building GDB with GCC's Undefined Behavior Sanitizer.
See the NEWS file for a more complete and detailed list of what this
release includes.
December 23rd, 2018: GDB 8.2.1 Released!
This is a minor corrective release over GDB 8.2, fixing the following
issues:
* 23516 (gdb build error under msys+mingw: strip can't handle
gdb-add-index.exe)
* 23623 (install-strip fails)
* 23626 (gdb crashes in upstream rust nil-enum test)
* 23650 (rust field name access error mentions "foo")
* 23663 (gdb 8.1.1: undefined rpl_stat function with musl
toolchains)
* 23669 (gdb.execute("show commands") doesn't work)
* 23714 (Command repetition stops working after gdb.execute)
* 23838 (8.2 regression for invalid -data-directory)
* 23974 ("info os" crash when specifying invalid object)
* 23999 (SYMBOL_LANGUAGE assertion failure on AIX)
* 24003 (Error when binary searching CUs for a specific DIE when
using DWZ)
September 5th, 2018: GDB 8.2 Released!
This version of GDB includes the following changes and enhancements:
* Support for the following target has been added:
- RiscV ELF (riscv*-*-elf)
* Support for following targets and native configurations has been
removed:
- m88k running OpenBSD (m88*-*-openbsd*)
- SH-5/SH64 ELF (sh64-*-elf*)
- SH-5/SH64 (sh*)
- SH-5/SH64 running GNU/Linux (sh*-*-linux*)
- SH-5/SH64 running OpenBSD (sh*-*-openbsd*)
* Various Python API enhancements
* Aarch64/Linux enhancements:
- SVE support.
- Hardware watchpoints improvements for entities stored at unaligned
addresses.
- New "c" response to disable the pager for the rest of the
current command.
- C expressions can now use _Alignof, and C++ expressions can now
use alignof.
- Improved flexibility for loading symbol files.
- The 'info proc' command nows works on running processes on
FreeBSD systems as well as core files created on FreeBSD
systems.
- A new --enable-codesign=CERT configure option to automatically
codesign GDB after build (useful on MacOS X).
See the NEWS file for a more complete and detailed list of what
this release includes.
pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
local changes: use plist var for gcore.
XXX don't install gcore.1 that doesn't appear to be installed but exists
remove merged patches.
GDB 8.1 includes the following changes and enhancements:
* Breakpoints on C++ functions are now set on all scopes by default
("wild" matching);
* Support for inserting breakpoints on functions marked with C++ ABI tags;
* Target floating-point arithmetic emulation during expression evaluation
(requires MPFR 3.1 or later);
* Various Python Scripting enhancements;
* Improved Rust support; in particular, Trait objects can now be inspected
when debugging Rust code;
* GDB no longer makes assumptions about the type of symbols without
debugging information to avoid producing erroneous and often confusing
results;
* The 'enable' and 'disable' commands now accept a range of breakpoint
locations;
* New 'starti' command to start the program at the first instruction;
* New 'rbreak' command to insert a number of breakpoints via a regular
expression pattern (requires Python);
* The 'ptype' command now supports printing the offset and size of
the fields in a struct;
* The 'gcore' command now supports dumping all the memory mappings
('-a' command-line option);
* New shortcuts for TUI Single-Key mode: 'i' for stepi, and 'o' for nexti;
* GDBserver enhancements:
** Support for transmitting environment variables to GDBserver;
** Support for starting inferior processes with a specified initial
working directory;
** On Unix systems, support for globbing expansion and variable
substitution of inferior command-line arguments;
* Various completion enhancements;
* The command used to compile and inject code with the 'compile' command
is now configurable;
* New '--readnever' command-line option to speed the GDB startup when
debugging information is not needed;
* Support for the following new native configurations:
** FreeBSD/aarch64 (aarch64*-*-freebsd*);
** FreeBSD/arm (arm*-*-freebsd*);
* Support for the following new targets:
** FreeBSD/aarch64 (aarch64*-*-freebsd*);
** FreeBSD/arm (arm*-*-freebsd*);
** OpenRISC ELF (or1k*-*-elf)
* Removed support for the following targets and native configurations:
** Solaris2/x86 (i?86-*-solaris2.[0-9]);
** Solaris2/sparc (sparc*-*-solaris2.[0-9]);
For a complete list and more details on each item, please see the gdb/NEWS
file, available at:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-8.1-release
Unsorted entries in PLIST files have generated a pkglint warning for at
least 12 years. Somewhat more recently, pkglint has learned to sort
PLIST files automatically. Since pkglint 5.4.23, the sorting is only
done in obvious, simple cases. These have been applied by running:
pkglint -Cnone,PLIST -Wnone,plist-sort -r -F
pkgsrc specific changes
-----------------------
Set on NetBSD debug-dir to locale properly debug info of the base softwate:
--with-separate-debug-dir=/usr/lib/debug
Disable globally binutils, gprof, gold, gas, ld. These packages are shipped
separately in other packages.
Upstream changelog
==================
GDB 8.0.1 brings the following fixes and enhancements over GDB 8.0:
* PR breakpoint/21886 (Compressed MIPS code debugging impossible due to memory breakpoint misplacement)
* PR symtab/22002 (Assertion on debuggee built with -gdwarf-5 -fdebug-types-section)
* PR symtab/22003 (Incompatibility with -gdwarf-5 - DW_FORM_implicit_const)
* PR gdb/22046 (Regression on older kernels for T (stopped) processes)
* PR sim/20863 (gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD)
* PR breakpoint/21555 ("error re-setting breakpoint" on PIE executables)
* PR tdep/21717 ("print $fpscr" says "<unavailable>" until some VFP data register is printed)
* PR exp/21827 (Regression: gdb command lookup became case-sensitive; but definitions are forced into lowercase)
* PR remote/22021 (Multi-arch exec fails with a remote target)
GDB 8.0 brings the following fixes and improvements, including:
* C++: Support for rvalue references
* Python scripting enhancements:
** New functions to start, stop and access a running btrace recording.
** Rvalue reference support in gdb.Type.
* GDB commands interpreter:
** User commands now accept an unlimited number of arguments.
** The "eval" command now expands user-defined arguments.
* DWARF version 5 support
(note that its .debug_names index is not supported yet).
* GDB/MI enhancements:
** New -file-list-shared-libraries command to list the shared
libraries in the program.
** New -target-flash-erase command, to erase flash memory.
* Support for native FreeBSD/mips (mips*-*-freebsd)
* Support for the following targets:
** Synopsys ARC (arc*-*-elf32)
** FreeBSD/mips (mips*-*-freebsd)
* Miscellaneous enhancements:
** Command-line redirection now supported on MS-Windows hosts.
** Support for thread names on MS-Windows.
** Support for the PKU register on GNU/Linux.
** Support for Target descriptions on sparc32 and sparc64.
** New GDB/CLI command to erase flash memory
** rdrand and rdseed instructions record/replay support.
Support for the following features have been removed:
* Support for Java programs compiled with gcj
* Support for the following configurations:
** FreeBSD/alpha (alpha*-*-freebsd*)
** GNU/kFreeBSD/alpha (alpha*-*-kfreebsd*-gnu)
For a complete list and more details on each item, please see the
gdb/NEWS file.
Define DBREG_DRX when it's undefined to:
#define DBREG_DRX(d,x) ((d)->dr[(x)])
This has been copied from FreeBSD:
/usr/include/x86/reg.h:#define DBREG_DRX(d,x) ((d)->dr[(x)])
No functional change for existing operating systems.
Sponsored by <The NetBSD Foundation>
build, but not linked at runtime. Fixes PLIST conflict with
devel/binutils and subsequently makes pbulk on (at least) SunOS
happy. This follows what e.g. ports and homebrew already do.
Remove a leftover patch file while at it.
Bump PKGREVISION.
In-freeze, OK by wiz.
Changelog:
*** Changes in GDB 7.11
* GDB now supports debugging kernel-based threads on FreeBSD.
* Per-inferior thread numbers
Thread numbers are now per inferior instead of global. If you're
debugging multiple inferiors, GDB displays thread IDs using a
qualified INF_NUM.THR_NUM form. For example:
(gdb) info threads
Id Target Id Frame
1.1 Thread 0x7ffff7fc2740 (LWP 8155) (running)
1.2 Thread 0x7ffff7fc1700 (LWP 8168) (running)
* 2.1 Thread 0x7ffff7fc2740 (LWP 8157) (running)
2.2 Thread 0x7ffff7fc1700 (LWP 8190) (running)
As consequence, thread numbers as visible in the $_thread
convenience variable and in Python's InferiorThread.num attribute
are no longer unique between inferiors.
GDB now maintains a second thread ID per thread, referred to as the
global thread ID, which is the new equivalent of thread numbers in
previous releases. See also $_gthread below.
For backwards compatibility, MI's thread IDs always refer to global
IDs.
* Commands that accept thread IDs now accept the qualified
INF_NUM.THR_NUM form as well. For example:
(gdb) thread 2.1
[Switching to thread 2.1 (Thread 0x7ffff7fc2740 (LWP 8157))] (running)
(gdb)
* In commands that accept a list of thread IDs, you can now refer to
all threads of an inferior using a star wildcard. GDB accepts
"INF_NUM.*", to refer to all threads of inferior INF_NUM, and "*" to
refer to all threads of the current inferior. For example, "info
threads 2.*".
* You can use "info threads -gid" to display the global thread ID of
all threads.
* The new convenience variable $_gthread holds the global number of
the current thread.
* The new convenience variable $_inferior holds the number of the
current inferior.
* GDB now displays the ID and name of the thread that hit a breakpoint
or received a signal, if your program is multi-threaded. For
example:
Thread 3 "bar" hit Breakpoint 1 at 0x40087a: file program.c, line 20.
Thread 1 "main" received signal SIGINT, Interrupt.
* Record btrace now supports non-stop mode.
* Support for tracepoints on aarch64-linux was added in GDBserver.
* The 'record instruction-history' command now indicates speculative execution
when using the Intel Processor Trace recording format.
* GDB now allows users to specify explicit locations, bypassing
the linespec parser. This feature is also available to GDB/MI
clients.
* Multi-architecture debugging is supported on AArch64 GNU/Linux.
GDB now is able to debug both AArch64 applications and ARM applications
at the same time.
* Support for fast tracepoints on aarch64-linux was added in GDBserver,
including JIT compiling fast tracepoint's conditional expression bytecode
into native code.
* GDB now supports displaced stepping on AArch64 GNU/Linux.
* "info threads", "info inferiors", "info display", "info checkpoints"
and "maint info program-spaces" now list the corresponding items in
ascending ID order, for consistency with all other "info" commands.
* In Ada, the overloads selection menu has been enhanced to display the
parameter types and the return types for the matching overloaded subprograms.
* New commands
maint set target-non-stop (on|off|auto)
maint show target-non-stop
Control whether GDB targets always operate in non-stop mode even if
"set non-stop" is "off". The default is "auto", meaning non-stop
mode is enabled if supported by the target.
maint set bfd-sharing
maint show bfd-sharing
Control the reuse of bfd objects.
set debug bfd-cache
show debug bfd-cache
Control display of debugging info regarding bfd caching.
set debug fbsd-lwp
show debug fbsd-lwp
Control display of debugging info regarding FreeBSD threads.
set remote multiprocess-extensions-packet
show remote multiprocess-extensions-packet
Set/show the use of the remote protocol multiprocess extensions.
set remote thread-events
show remote thread-events
Set/show the use of thread create/exit events.
set ada print-signatures on|off
show ada print-signatures"
Control whether parameter types and return types are displayed in overloads
selection menus. It is activaled (@code{on}) by default.
set max-value-size
show max-value-size
Controls the maximum size of memory, in bytes, that GDB will
allocate for value contents. Prevents incorrect programs from
causing GDB to allocate overly large buffers. Default is 64k.
* The "disassemble" command accepts a new modifier: /s.
It prints mixed source+disassembly like /m with two differences:
- disassembled instructions are now printed in program order, and
- and source for all relevant files is now printed.
The "/m" option is now considered deprecated: its "source-centric"
output hasn't proved useful in practice.
* The "record instruction-history" command accepts a new modifier: /s.
It behaves exactly like /m and prints mixed source+disassembly.
* The "set scheduler-locking" command supports a new mode "replay".
It behaves like "off" in record mode and like "on" in replay mode.
* Support for various ROM monitors has been removed:
target dbug dBUG ROM monitor for Motorola ColdFire
target picobug Motorola picobug monitor
target dink32 DINK32 ROM monitor for PowerPC
target m32r Renesas M32R/D ROM monitor
target mon2000 mon2000 ROM monitor
target ppcbug PPCBUG ROM monitor for PowerPC
* Support for reading/writing memory and extracting values on architectures
whose memory is addressable in units of any integral multiple of 8 bits.
* New remote packets
exec stop reason
Indicates that an exec system call was executed.
exec-events feature in qSupported
The qSupported packet allows GDB to request support for exec
events using the new 'gdbfeature' exec-event, and the qSupported
response can contain the corresponding 'stubfeature'. Set and
show commands can be used to display whether these features are enabled.
vCtrlC
Equivalent to interrupting with the ^C character, but works in
non-stop mode.
thread created stop reason (T05 create:...)
Indicates that the thread was just created and is stopped at entry.
thread exit stop reply (w exitcode;tid)
Indicates that the thread has terminated.
QThreadEvents
Enables/disables thread create and exit event reporting. For
example, this is used in non-stop mode when GDB stops a set of
threads and synchronously waits for the their corresponding stop
replies. Without exit events, if one of the threads exits, GDB
would hang forever not knowing that it should no longer expect a
stop for that same thread.
N stop reply
Indicates that there are no resumed threads left in the target (all
threads are stopped). The remote stub reports support for this stop
reply to GDB's qSupported query.
QCatchSyscalls:1 [;SYSNO]...
QCatchSyscalls:0
Enable ("QCatchSyscalls:1") or disable ("QCatchSyscalls:0")
catching syscalls from the inferior process.
syscall_entry stop reason
Indicates that a syscall was just called.
syscall_return stop reason
Indicates that a syscall just returned.
QCatchSyscalls:1 in qSupported
The qSupported packet may now include QCatchSyscalls:1 in the reply
to indicate support for catching syscalls.
* Extended-remote exec events
** GDB now has support for exec events on extended-remote Linux targets.
For such targets with Linux kernels 2.5.46 and later, this enables
follow-exec-mode and exec catchpoints.
set remote exec-event-feature-packet
show remote exec-event-feature-packet
Set/show the use of the remote exec event feature.
* Thread names in remote protocol
The reply to qXfer:threads:read may now include a name attribute for each
thread.
* Target remote mode fork and exec events
** GDB now has support for fork and exec events on target remote mode
Linux targets. For such targets with Linux kernels 2.5.46 and later,
this enables follow-fork-mode, detach-on-fork, follow-exec-mode, and
fork and exec catchpoints.
* Remote syscall events
** GDB now has support for catch syscall on remote Linux targets,
currently enabled on x86/x86_64 architectures.
set remote catch-syscall-packet
show remote catch-syscall-packet
Set/show the use of the remote catch syscall feature.
* MI changes
** The -var-set-format command now accepts the zero-hexadecimal
format. It outputs data in hexadecimal format with zero-padding on the
left.
* Python Scripting
** gdb.InferiorThread objects have a new attribute "global_num",
which refers to the thread's global thread ID. The existing
"num" attribute now refers to the thread's per-inferior number.
See "Per-inferior thread numbers" above.
** gdb.InferiorThread objects have a new attribute "inferior", which
is the Inferior object the thread belongs to.
Changelog:
December 5th, 2015: GDB 7.10.1 Released!
The latest version of GDB, version 7.10.1, is available for download.
This is a minor corrective release over GDB 7.10, fixing the following issues:
PR remote/18965 (new vforkdone stop reply should indicate parent process ID)
PR gdb/18957 (build failure in linux-namespaces.c due to setns static declaration)
PR gdb/19297 (Internal error on "record btrace": Unexpected branch trace format)
PR c++/16957 (gdb segfaults when loading symbols in C++11-enabled application)
PR c++/19306 (Incorrect demangling of symbols with ABI tags)
PR c++/19307 (Demangler bugs found with fuzz-testing)
PR c++/19308 (Demangle C++ Transactional Memory TS (N4514) symbols)
August 28th, 2015: GDB 7.10 Released!
The latest version of GDB, version 7.10, is available for download.
Changes in this release include:
Improved support for accessing shared libraries directly from the target system when debugging remotely.
Various Guile and Python scripting improvements.
Record-replay and reverse debugging on Aarch64 Linux.
Support for fork events on extended-remote Linux targets (Linux kernels 2.5.60 and later).
DTrace USDT (Userland Static Defined Tracing) probes support on x86_64 GNU/Linux targets.
Vector ABI support on S/390 GNU/Linux targets.
GDB now reads the GDBHISTSIZE environment variable rather than HISTSIZE to determine the size of GDB's command history.
Support for setting the parity when connecting to the target using a serial interface.
The number of candidates to be considered during completion can now be limited.
Support for Sun's version of the "stabs" debug file format has been removed.
Support for HP/PA running HP-UX (hppa*-*-hpux*) has been removed.
Support for Itanium running HP-UX (ia64-*-hpux*) has been removed.
See the NEWS file for a more complete and detailed list of what this release includes.
Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.