• GDB_7.7_Release

GDB 7.7.x Release Management

[NAME] at the beginning of each item is the name of a point of contact who will help trying to get the issue fixed faster.

Current Status

• 2014-01-08: The 7.7 branch has been created (gdb-7.7-branch).

• 2014-01-08: The GDB 7.6.90 pre-release has been published.
• 2014-02-06: The GDB 7.7 Release has been published.
• 2014-05-05: The GDB 7.7.1 Release has been published.

Unreleased Fixes

The following fixes have been made to the branch since GDB 7.7.1 was released. We are not planning on making another release off that branch unless absolutely necessary. But the following fixes may be of use for someone using the tip of that branch.

• PR tdep/16940 (S390: 64-bit GDB can't debug multithreaded 31-bit inferior)

Fixes in GDB 7.7.1

GDB 7.7.1 brings the following fixes and improvements:

• 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)

Todo:

The GDB 7.7 release

Todo:

Optional (?):

Done:

• [Yao?] Regression when loading a trace file

  • https://www.sourceware.org/ml/gdb/2014-01/msg00031.html

  • https://www.sourceware.org/ml/gdb-patches/2014-01/msg01054.html

• [Doug] Fix PR 16426: memory corruption (use after free) with fission

  • https://sourceware.org/bugzilla/show_bug.cgi?id=16426

• [Tom] PR python/16485 python exception in frame filter code.

• [Tom] PR python/16487 crash in py-framefilter.c

• [Tom] PR python/16491 crash in py-framefilter.c

Excluded:

Post Branch-Creation (for the NEXT release cycle)

Todo:

• [Joel] Clean windows-nat and gdbserver/win32-low up regarding LOAD_DLL_DEBUG_EVENTs occurring during the inferior intialization phase.

  • http://www.sourceware.org/ml/gdb-patches/2013-12/msg00073.html

Done:

Before Branch Creation

Todo:

Optional (?):

Done:

• [Pierre Muller] Fix PR 16201: internal error on a cygwin program linked against a DLL with no .data section

  • https://sourceware.org/ml/gdb-patches/2013-11/msg00865.html

• [Jan] Support .dwp with the name of symlinked binary file

  • https://sourceware.org/ml/gdb-patches/2013-09/msg00167.html

• [Jan] Improve Executable displayed path (PR 15415 regression kind #2)

  • https://sourceware.org/ml/gdb-patches/2013-09/msg00865.html

• [Doug] DWP Version 2 support
• [Joel] Update release scripts turning off development mode

  • See: [http://www.sourceware.org/ml/gdb-patches/2013-06/msg00276.html]

• Update gdbadmin scripts re: version.in change.
  • Change update-cvs-version for branch handling (on HEAD, script should not be necessary)
  • Update crontab calling this script

• [Jan/Doug] Record objfile->original_name as an absolute path

  • https://sourceware.org/ml/gdb-patches/2013-10/msg00275.html

• [Joel] GDB/MI solib regression.

  • http://www.sourceware.org/ml/gdb-patches/2013-10/msg00850.html

  • The fix: http://www.sourceware.org/ml/gdb-patches/2013-12/msg00559.html

• [dje] Fix PR 16286: value.string(length = x) broken for common variable length arrays idiom

  • https://sourceware.org/ml/gdb-patches/2013-12/msg00052.html

• [Sergio Durigan Junior] Fix PR tdep/15653: Implement SystemTap SDT probe support for AArch64

  • https://sourceware.org/ml/gdb-patches/2013-12/msg00812.html

• Adjust version-date update script.
  • On branch master, we rely on binutils for doing the daily update. On the GDB release branch, on the other hand, we need to do it ourselves.

  • It turns out that the script currently in use should be good enough, AFAICT. The crontab has been adjusted to use bfd/version.h instead of gdb/version.in. We will get an error email if the update fails, and fix as needed.

Excluded:

• [PhilippeW] "catch syscall" with gdbserver (not ready in time)

  • https://sourceware.org/ml/gdb-patches/2013-08/msg00922.html