From: Tobias Hahn <tobias.hahn@ableton.com>
To: gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.0.1 released!
Date: Tue, 05 Jan 2010 22:54:00 -0000 [thread overview]
Message-ID: <4F6D3FFB-7ED7-4DDA-96FD-4A2D7392E42F@ableton.com> (raw)
In-Reply-To: <announce.20091222180523.GA12693@adacore.com>
Sorry if this a FAQ, but is there a place where the current x86/x86_64 Darwin status is tracked, in particular support for debugging dylibs and the missing symbols issue (which can be worked around using dsymutil)?
Best, Tobias
Am 22.12.2009 um 19:05 schrieb Joel Brobecker:
> GDB 7.0.1 released!
>
> Release 7.0.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
> 17MB 53ebade39bfdc1d06744e5188b6438b1 gdb-7.0.1.tar.bz2
> 23MB 100d6e5524be1a34ba61556a7389a297 gdb-7.0.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.0.1 is a minor corrective release. The following fixes have been
> made over GDB 7.0 (release Oct 06, 2009):
>
> * GDB Crash due to stack overflow (PR gdb/10457);
> * Build failure on newer versions of FreeBSD;
> * Crash on solaris when reading symbols (PR gdb/10819);
> * Thumb2 debugging support;
> * Build failure on IRIX 5.3 (MAP_FAILED not defined);
> * Buffer overflow during function epilogue analysis
> (debuggers targeted for x86_64 only);
> * Crash trying to complete the "catch exception" command;
> * GDB freeze (infinite loop);
> * GDB Crash accessing printing structure with bitfield (PR gdb/10884);
> * Various testsuite fixes (not affecting the debugger);
> * The manual now provides the correct GPL version licensing text.
> Similarly, file gdb/COPYING now provides the text of the GPL version 3.
>
> GDB 7.0 featured new platforms being supported, major new features,
> enhancements and bug fixes. For a complete list and more details on each
> iteam, please see the gdb/NEWS file.
>
> The new native configurations being supported are:
>
> * x86/x86_64 Darwin
> * x86_64 MinGW
>
> Support for the following targets has been added:
>
> * Lattice Mico32
> * x86/x86_64 DICOS
> * S+core 3
> * The remote stub now supports x86 Windows CE
>
> The major new features are:
>
> * Python scripting support
> * Reverse debugging, Process record and replay
> * Non-stop debugging
> * Multi-architecture debugging
> * Multi-inferior, multi-process debugging
>
> It also features many enhancements and bug fixes, including:
>
> * GDB now has an interface for JIT compilation
> * Tracepoints may now be conditional
> * Multi-byte and wide character set support
> * New /r and /m modifiers for the "disassemble" command
> * Automatic retrieval of shared library files from remote targets
> * Inlined functions are now supported
> * New remote protocal packets
> * GDB is now able to read compressed debug sections
> * Thread switching is now supported on Tru64
> * Ada task switching is now supported
> * New features in gdbserver, the GDB remote stub
> * New command to stop execution when a system call is made
>
> --
> Joel
next prev parent reply other threads:[~2010-01-05 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 18:13 Joel Brobecker
2010-01-05 22:54 ` Tobias Hahn [this message]
2010-01-06 8:39 ` Tristan Gingold
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=4F6D3FFB-7ED7-4DDA-96FD-4A2D7392E42F@ableton.com \
--to=tobias.hahn@ableton.com \
--cc=gdb@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