[ANNOUNCEMENT] GDB 7.5.1 released!

[ANNOUNCEMENT] GDB 7.5.1 released!

[Joel Brobecker]

            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

RE: [ANNOUNCEMENT] GDB 7.5.1 released!

[Pierre Muller]

  Hi Joel,

  maybe I still don't understand how tarball signature is supposed to
work...
I never did that before ...

  But I tried to verify the signature of the latest 7.5.1 release,
but couldn't find the public key DSA keyFF325CF3
  I thought that all GNU software shoulb be signed using

Trying to find your key, I found this message:

http://lists.gnu.org/archive/html/bug-gdb/2006-01/msg00006.html

Where is the key?

Pierre

> -----Message d'origine-----
> De : gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la part
> de Joel Brobecker
> Envoyé : jeudi 29 novembre 2012 14:12
> À : gdb@sourceware.org
> Objet : [ANNOUNCEMENT] GDB 7.5.1 released!
> 
> 
>             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

Re: [ANNOUNCEMENT] GDB 7.5.1 released!

[Joel Brobecker]

>   But I tried to verify the signature of the latest 7.5.1 release, but
>   couldn't find the public key DSA keyFF325CF3 I thought that all GNU
>   software shoulb be signed using

I have never published my public key before, mostly because I wasn't
sure how to do it, and (almost) no one asked for it. I've just published
it on wwwkeys.pgp.net which, as I understand it, is part of a network
for key servers that synchronized each other.

    % gpg --search-keys --keyserver wwwkeys.pgp.net FF325CF3
    gpg: searching for "FF325CF3" from hkp server wwwkeys.pgp.net
    (1)     Joel Brobecker <brobecker@adacore.com>
              1024 bit DSA key FF325CF3, created: 2005-10-27

Let me know if there is anything else I need to do.

-- 
Joel

Re: [ANNOUNCEMENT] GDB 7.5.1 released!

[Hui Zhu]

On Sun, Dec 2, 2012 at 8:49 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>   But I tried to verify the signature of the latest 7.5.1 release, but
>>   couldn't find the public key DSA keyFF325CF3 I thought that all GNU
>>   software shoulb be signed using
>
> I have never published my public key before, mostly because I wasn't
> sure how to do it, and (almost) no one asked for it. I've just published
> it on wwwkeys.pgp.net which, as I understand it, is part of a network
> for key servers that synchronized each other.
>
>     % gpg --search-keys --keyserver wwwkeys.pgp.net FF325CF3
>     gpg: searching for "FF325CF3" from hkp server wwwkeys.pgp.net
>     (1)     Joel Brobecker <brobecker@adacore.com>
>               1024 bit DSA key FF325CF3, created: 2005-10-27
>
> Let me know if there is anything else I need to do.
>
> --
> Joel

Maybe we need wiki this message.

Thanks,
Hui

Re: [ANNOUNCEMENT] GDB 7.5.1 released!

[Alfred M. Szmidt]

   maybe I still don't understand how tarball signature is supposed to
   work...  I never did that before ...

   But I tried to verify the signature of the latest 7.5.1 release,
   but couldn't find the public key DSA keyFF325CF3 I thought that all
   GNU software shoulb be signed using

   Trying to find your key, I found this message:

   http://lists.gnu.org/archive/html/bug-gdb/2006-01/msg00006.html

   Where is the key?

It should be available at ftp.gnu.org as /gnu/gnu-keyring.gpg.

Re: [ANNOUNCEMENT] GDB 7.5.1 released!

[Joel Brobecker]

> It should be available at ftp.gnu.org as /gnu/gnu-keyring.gpg.

Indeed, I didn't know that. I verfied that my key is in that file.
I have updated the download page of the GDB website to explain
where to find the key necessary to verify release tarballs.
See http://www.sourceware.org/gdb/download/

Thanks for the tip,
-- 
Joel

RE: [ANNOUNCEMENT] GDB 7.5.1 released!

[Pierre Muller]

> -----Message d'origine-----
> De : gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la part
> de Joel Brobecker
> Envoyé : dimanche 2 décembre 2012 17:07
> À : Alfred M. Szmidt
> Cc : Pierre Muller; gdb@sourceware.org
> Objet : Re: [ANNOUNCEMENT] GDB 7.5.1 released!
> 
> > It should be available at ftp.gnu.org as /gnu/gnu-keyring.gpg.
> 
> Indeed, I didn't know that. I verfied that my key is in that file.
> I have updated the download page of the GDB website to explain
> where to find the key necessary to verify release tarballs.
> See http://www.sourceware.org/gdb/download/
>
Thanks Joel,

This is the result I get:
$ gpg --verify --keyring gnu-keyring.gpg gdb-7.5.1.tar.bz2.sig
gpg: Signature made Thu Nov 29 11:34:12 2012 CET using DSA key ID FF325CF3
gpg: Good signature from "Joel Brobecker <brobecker@adacore.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: F40A DB90 2B24 264A A42E  50BF 92ED B04B FF32 5CF3

  Is the WARNING unavoidable?

Pierre Muller

Re: [ANNOUNCEMENT] GDB 7.5.1 released!

[shawn wilson]

On Sun, Dec 2, 2012 at 2:31 PM, Pierre Muller
<pierre.muller@ics-cnrs.unistra.fr> wrote:
>

> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: F40A DB90 2B24 264A A42E  50BF 92ED B04B FF32 5CF3
>
>   Is the WARNING unavoidable?
>

it's a web of trust warning. should be correctable on your end.

Re: [ANNOUNCEMENT] GDB 7.5.1 released!

[Maciej W. Rozycki]

On Sun, 2 Dec 2012, shawn wilson wrote:

> <pierre.muller@ics-cnrs.unistra.fr> wrote:
> >
> 
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:          There is no indication that the signature belongs to the
> > owner.
> > Primary key fingerprint: F40A DB90 2B24 264A A42E  50BF 92ED B04B FF32 5CF3
> >
> >   Is the WARNING unavoidable?
> >
> 
> it's a web of trust warning. should be correctable on your end.

 On both ends at a time only actually, because for a path of trust to be 
available a key in question has to have verifiable third-party signatures 
(usually obtained in person at a key-signing session).

  Maciej