Bug#748317: libstdc++6: Pretty-printers don't support Python 3

Package: libstdc++6 Version: 4.9.0-3 Severity: important Control: affects -1 gdb Dear doko, On May 6, you NMU'd gdb to make it build against Python 3. Which would be all well and good, except for one thing: the pretty-printers for libstdc++ are *still* using Python 2 syntax. (Any particular reas

Processed: libstdc++6: Pretty-printers don't support Python 3

Processing control commands: > affects -1 gdb Bug #748317 [libstdc++6] libstdc++6: Pretty-printers don't support Python 3 Added indication that 748317 affects gdb -- 748317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748317 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#748315: libgcc1: GDB could use SystemTap SDT probes

Package: libgcc1 Version: 1:4.7.2-5 Severity: normal Control: affects -1 gdb Dear Maintainer, GDB (since version 7.5) could take advantage of SystemTap probes in libgcc/libstc++ to allow "next" and the like to work properly when exceptions are thrown, even without the debugging symbols installed.

Processed: libgcc1: GDB could use SystemTap SDT probes

Processing control commands: > affects -1 gdb Bug #748315 [libgcc1] libgcc1: GDB could use SystemTap SDT probes Added indication that 748315 affects gdb -- 748315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --

Bug#748298: please drop the sjlj support

Package: gnat-4.9 Version: 4.9.0-1 Severity: important Tags: sid jessie Building the gnat libraries for both the zcx and sjlj exception support is not needed anymore for Debian, and the local patches are done in a rather hackish way which prevents cross-building of the compiler. Please drop these

Bug#748297: the libgnatprj and libgnatvsn patches should be upstreamed or dropped

Package: gnat-4.9 Version: 4.9.0-1 Severity: important Tags: sid jessie Building the gnatprj and gnatvsn libraries is done with a rather hackish local patch, which doesn't integrate at all with the current GCC packaging. Worst things are not using the just built toolchain for the package builds,

Re: preparing for GCC 4.9 (bug squashing on May 16/17)

+++ Matthias Klose [2014-05-13 14:56 +0200]: > With gcc-4.9 now available in testing, it is time to prepare for the change of > the default to 4.9, for a subset of architectures or for all (release) > architectures. The defaults for the gdc, gccgo, gcj and gnat frontends > already > point to 4.9