From: Joel Brobecker <brobecker@adacore.com>
To: gdb-announce@sourceware.org
Subject: GDB 7.5.1 released!
Date: Thu, 29 Nov 2012 13:18:00 -0000 [thread overview]
Message-ID: <20121129131213.GA21542@adacore.com> (raw)
GDB 7.5.1 released!
Release 7.5.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
21MB 3f48f468b24447cf24820054ff6e85b1 gdb-7.5.1.tar.bz2
28MB b1519bf899890d21d4774845a6e602fe gdb-7.5.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 CVS 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.5.1 is a minor corrective release over GDB 7.5, and includes
fixes for the following problems:
- strict-aliasing warnings in libiberty/md5.c generated by GCC 4.7.
- An "Attempt to dereference a generic pointer" error (-var-create).
This error only occurs when the "print object" setting is "on".
- Backtrace problems on x32 (PR backtrace/14646).
- next/step/finish problems on x32 (PR gdb/14647).
- A "malformed linespec error: unexpected keyword, [...]" error
(PR breakpoints/14643)
- GDB crash while stepping through powerpc (32bits) code.
- A failed assertion in linux_ptrace_test_ret_to_nx.
- A "!frame_id_inlined_p (frame_id)" failed assertion.
- A "No more reverse-execution history." error during reverse "next"
execution (PR 14548).
- Incomplete command descriptions in "apropos" output.
- PR gdb/14494 (a GDB crash difficult to characterize).
- A build warning in allocate_symtab when building on x86_64-windows.
GDB 7.5.1 also brings the following improvements:
- Offer some helpful tips when detecting a file/script for which
auto-loading has been declined.
- Special handling of program's '.exe' suffix when searching for
auto-load-able scripts.
GDB 7.5 brings new targets, features and improvements, including:
* Go language support.
* New targets (x32 ABI, microMIPS, Renesas RL78, HP OpenVMS ia64).
* More Python scripting improvements.
* SDT (Static Defined Tracing) probes support with SystemTap probes.
* GDBserver improvements (stdio connections, target-side evaluation
of breakpoint conditions, remote protocol improvements).
* Other miscellaneous improvements (ability to stop when a shared
library is loaded/unloaded, dynamic printf, etc).
* Reverse debugging on ARM.
* The binary "gdbtui" has been abandoned and can no longer be built.
Use "gdb -tui" instead.
For a complete list and more details on each item, please see the
gdb/NEWS file.
--
Joel
reply other threads:[~2012-11-29 13:18 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=20121129131213.GA21542@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-announce@sourceware.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).