public inbox for gdb-announce@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-announce@sourceware.org, info-gnu@gnu.org
Subject: GDB 7.7.1 released!
Date: Mon, 05 May 2014 22:39:00 -0000	[thread overview]
Message-ID: <20140505223807.EF064E075F@joel.gnat.com> (raw)



            GDB 7.7.1 released!

Release 7.7.1 of GDB, the GNU Debugger, is now available via anonymous
FTP.  GDB is a source-level debugger for Ada, C, C++, Objective-C,
Pascal and many other languages.  GDB can target (i.e., debug programs
running on) more than a dozen different processor architectures, and GDB
itself can run on most popular GNU/Linux, Unix and Microsoft Windows
variants.

You can download GDB from the GNU FTP server in the directory:

        ftp://ftp.gnu.org/gnu/gdb

The vital stats:

  Size   md5sum                            Name
  24MiB  77b20b515e7c25f032cb9732a66620fe  gdb-7.7.1.tar.bz2
  31MiB  45b07b53d81832d32ccd4829465d4886  gdb-7.7.1.tar.gz

There is a web page for GDB at:

        http://www.gnu.org/software/gdb/

That page includes information about GDB mailing lists (an announcement
mailing list, developers discussion lists, etc.), details on how to
access GDB's source repository, locations for development snapshots,
preformatted documentation, and links to related information around
the net.  We will put errata notes and host-specific tips for this release
on-line as any problems come up.  All mailing lists archives are also
browsable via the web.

GDB 7.7.1 provides the following fixes and improvements to GDB 7.7:

  * PR win32/14018 (pc register not available error on Windows)
  * PR python/16547 (GDB crashing on gdb.python/py-linetable.exp)
  * PR build/16550 (64-bit GDB doesn't build on Solaris)
  * PR gdb/16626 (auto-load regression: gdb uses wrong file to test safeness)
  * PR breakpoints/16292 (GDB oversteps a range in some cases.)
  * PR gdb/16575 (stale breakpoint instructions in the code cache)
  * PR gdb/16696 (AIX 32-bit cores, high section addresses)
  * PR gdb/16721 (Erroneous backtrace on AVR)
  * PR gdb/16832 (Erroneous backtrace on avrxmega architectures)
  * PR build/16873 (GDB 7.7 does not build with GCC 4.9)

GDB 7.7 brings new targets, features and improvements, including:

  * C++:

    ** GDB now implements the 'typeid' operator.
    ** Exception Catchpoints can now filter by type.

  * Python scripting:

    ** Frame filters and frame decorators have been added.
    ** Temporary breakpoints are now supported.
    ** Line tables representation has been added.
    ** New attribute 'parent_type' for gdb.Field objects.
    ** gdb.Field objects can be used as subscripts on gdb.Value objects.
    ** New attribute 'name' for gdb.Type objects.

  * New commands:

    ** show configuration
    ** catch rethrow
    ** info exceptions [REGEXP]
    ** remove-symbol-file [FILENAME | -a ADDRESS]
    ** maint check-psymtabs
    ** maint check-symtabs
    ** maint expand-symtabs
    ** maint set|show per-command [space | time | symtab]

  * New options:

    ** set|show debug symfile off|on
    ** set|show print raw frame-arguments
    ** set|show remote trace-status-packet
    ** set|show debug nios2
    ** set|show range-stepping
    ** set|show startup-with-shell
    ** set|show code-cache

    For all options that interpret 0 or -1 as meaning "unlimited",
    the literal 'unlimited' can ot be used.

  * New convenience variables/functions:
    ** $_exception
    ** $_exitsignal
    ** $_isvoid

  * GDB/MI:

    ** All MI commands now accept an optional "--language" option.
    ** "undefined-command" error code provided in "^error" result
       records when trying to run a non-existing command.
    ** New commands -catch-assert and -catch-exceptions
    ** New command -info-ada-exceptions
    ** New command -info-gdb-mi-command
    ** New command -dprintf-insert
    ** New command -trace-frame-collected
    ** -trace-save CTF (Common Trace Format) support.
    ** -data-list-register-values, -stack-list-locals, -stack-list-arguments
       and -stack-list-variables optional "--skip-unavailable" option.
    ** -exec-run optional "--start" option.

  * Remote Protocol:

    ** Target-assigned range stepping support.
       GDBserver implements this feature on x86/x86_64 GNU/Linux targets.
    ** vCont new 'r' action.
    ** qXfer:libraries-svr4:read's annex used to pass argument list.

  * New target configurations:

    ** Nios II ELF                     nios2*-*-elf
    ** Nios II GNU/Linux               nios2*-*-linux
    ** Texas Instruments MSP430        msp430*-*-elf

  * GDB Windows x64 unwinding data support.

  * SystemTap SDT probes support on AArch64 GNU/Linux.

  * The 'tsave' command now supports CTF (Common Trace Format).

  * New script gcore, installed in $prefix/bin

  * New script contrib/gdb-add-index.sh for adding .gdb_index sections
    to binaries.

  * Improve arm*-linux record/replay support.

  * Removed support for a.out NetBSD and OpenBSD obsolete configurations.
    ELF variants of these configurations are kept supported.

  * The "set|show remotebaud" commands are deprecated. Use "show|show serial
    baud" instead.

For a complete list and more details on each item, please see the
gdb/NEWS file.

-- 
Joel Brobecker

                 reply	other threads:[~2014-05-05 22:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140505223807.EF064E075F@joel.gnat.com \
    --to=brobecker@adacore.com \
    --cc=gdb-announce@sourceware.org \
    --cc=info-gnu@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).