public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/16550] bfd/cache.c doesn't compile with gcc -m64 on Solaris Date: Mon, 05 May 2014 21:54:00 -0000 [thread overview] Message-ID: <bug-16550-4717-CoKEpYT8nD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16550-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16550 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The annotated tag, gdb-7.7.1-release has been created at af2cd04ccdd7631f4009b2aef5c8402b97d732e6 (tag) tagging 4bd8fc3a1362970d9800a263987af8093798338b (commit) replaces gdb-7.7-release tagged by Joel Brobecker on Mon May 5 14:53:19 2014 -0700 - Log ----------------------------------------------------------------- GDB 7.7.1 Release. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEABECAAYFAlNoCE8ACgkQku2wS/8yXPMbgQCgiCmLYGN3tjnqEEc0Y0i4iCHj RN8AnRgphFx5RnfZ5TSUHgC6mVHel7sC =xfEO -----END PGP SIGNATURE----- Eli Zaretskii (1): PR gdb/14018 -- avoid "PC register not available" errors. GDB Administrator (88): Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Automatic date update in version.in Jan Kratochvil (3): Fix Python stack corruption PR gdb/16626 PR gdb/16626 Joel Brobecker (3): Document the GDB 7.7 release in gdb/ChangeLog Bump GDB version number to 7.7.0.DATE-cvs. Set GDB version number to 7.7.1. Nick Clifton (1): Following up on Tom's suggestion I am checking in a patch to replace the various Pedro Alves (3): Make sure we don't resume the stepped thread by accident. PR gdb/16575: stale breakpoint instructions in the code cache AIX 32-bit core loading, high section addresses. Pierre Langlois (1): Erroneous backtrace on AVR. Rainer Orth (1): PR build/16550 ----------------------------------------------------------------------- -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-05-05 21:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-10 14:11 [Bug build/16550] New: " ro at CeBiTec dot Uni-Bielefeld.DE 2014-02-10 15:28 ` [Bug build/16550] " cvs-commit at gcc dot gnu.org 2014-02-10 15:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2014-05-05 21:54 ` cvs-commit at gcc dot gnu.org [this message]
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=bug-16550-4717-CoKEpYT8nD@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).