SRU: gdb 7.7.1 for trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdb (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU: gdb 7.7.1 for trusty
The SRU supersedes #1328503, building the gdb-doc package now from the gdb source, with the gdb man page in the gdb package, and updates to the 7.7.1 release.
7.7.1 is a bug fix release (https:/
PR win32/14018 (pc register not available error on Windows)
PR python/16547 (GDB crashing on gdb.python/
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)
The gdb package was built in the ubuntu-
SRU Justification:
[Impact]
Some crashes and misbehaviour.
[Test Case]
Run the gdb testsuite and check that the added testcases pass
[Regression Potential]
The gdb 7.7.1 was available in 14.10 until replaced by 7.8, and didn't show any issues.
Related branches
Changed in gdb (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
Hello Matthias, or anyone else affected,
Accepted gdb into trusty-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ gdb/7.7. 1-0ubuntu5~ 14.04.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!