Your message dated Sun, 18 Dec 2016 01:03:41 +0000 with message-id <[email protected]> and subject line Bug#814558: fixed in gdb 7.12-4 has caused the Debian Bug report #814558, regarding libglib2.0-0-dbg: GDB backtrace decoration broken to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 814558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814558 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libglib2.0-0-dbg Version: 2.47.5-1 Severity: normal Dear Maintainer, whenever I have GDB output a backtrace containing GLib functions, I get something like this instead of informative lines about said functions: Python Exception <class 'SystemError'> <built-in function isinstance> returned a result with an error set: After setting GDB's ``python print-stack`` option to ``full``, I get this additional detail: #0 0xffffffff in OverflowError: Python int too large to convert to C long During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/gdb/python/gdb/FrameDecorator.py", line 97, in function if not isinstance(self._base, gdb.Frame): SystemError: <built-in function isinstance> returned a result with an error set I can provide a minimal example if you want, but really on my system this happens with any program containing GLib or related functions (including GTK+). Just set a breakpoint on one of them and tell GDB to print a backtrace. It doesn't happen with any other library's functions that I know of. I figured I'd file this bug for libglib2.0-0-dbg because it probably has something to do with those GDB auto-load Python scripts, e.g. libglib-2.0.so.0.4705.0-gdb.py. Not 100% sure though, what do you think? Might well be my fault. Tested this with the "testing" (2.46.2-3) as well as "experimental" (2.47.5-1) package versions. Cheers -- System Information: Debian Release: stretch/sid APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libglib2.0-0-dbg depends on: ii libglib2.0-0 2.47.5-1 libglib2.0-0-dbg recommends no packages. libglib2.0-0-dbg suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: gdb Source-Version: 7.12-4 We believe that the bug you reported is fixed in the latest version of gdb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez <[email protected]> (supplier of updated gdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 18 Dec 2016 01:44:24 +0100 Source: gdb Binary: gdb gdb-python2 gdb-minimal gdb-multiarch gdbserver gdb-source Architecture: source Version: 7.12-4 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez <[email protected]> Changed-By: Héctor Orón Martínez <[email protected]> Description: gdb - GNU Debugger gdb-minimal - GNU Debugger (minimal version) gdb-multiarch - GNU Debugger (with support for multiple architectures) gdb-python2 - GNU Debugger (linked against python2) gdb-source - GNU Debugger (source) gdbserver - GNU Debugger (remote server) Closes: 814558 848362 Changes: gdb (7.12-4) unstable; urgency=medium . * debian/sanitize-gdb.sh: drop chm from doc tarball as well. - lintian complains *.chm files are included without sources * Revert "debian/control: declare gdb{,-python2} m-a same" (Closes: #848362) * debian/patches: fix python framefilter. - get address as long instead of unsigned long. (Closes: #814558) * debian/gbp.conf: add upstream branch, pristine-tar. Checksums-Sha1: 6d787ac8d84bb3bda42c385ed451da4454943a5d 2846 gdb_7.12-4.dsc 79f4de358a4ea50fa38c1f337fda30d4e75cae80 61500 gdb_7.12-4.debian.tar.xz Checksums-Sha256: 985c58cab571f6598eb7b8aa8fd88c2b9f5dfbb4e579a91e454d73f747aeaaad 2846 gdb_7.12-4.dsc 681dc0f39fe0ffdd1274426c676a1349f1b362de31c4607dca2c81953e591e17 61500 gdb_7.12-4.debian.tar.xz Files: c9a0adc0c9915225d64e010788ea9147 2846 devel optional gdb_7.12-4.dsc c61d0a79648fd2dad5c2043399639647 61500 devel optional gdb_7.12-4.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAlhV3Q0ACgkQryKDqnbi rHvaeRAAiiOSMEJlN2EXQib9/OLrzhbv3lgT5VtyFsiAhyJ9HA5V/sOhqiWw9QNq wgbu8WPbsvHJ8ms52uV4BYhUO4DAsJ/RUGGIWLYn4uMckLpi26ECYS2HIzvsxm+D a7Fog8DwS3+wigxIiOJUW685BhpL8IQ9tUZQsS1VEiVmyK6Cgzrpv03CwZjMwTQl 0LgQsgaT7N6fj+CJXtMmx2VpFB8GcA0LkKejE0AFvYem72R955h+xbvR4QTcc5I5 Kce5tHcTTckDWYUohpAip0wpv8w3ypbWIVvZt0EAd2zcsu1l3E9A+0tbXpN8Nlwh sYBZUXJs58ROJI8zOScBhlz3IAS5cfZYOd6UTENQk7T48woF7dnytV8oFmZv4ODS Up1wriaosCqY6uQL2KIe/7cjslwZfDrGMVkdFDADcZADNgZODxdvigtu/qHYox0x PX8lwSAc2WhZXkgDrY9wzIQwpOpPfwdlPraY9ZEDBLkiFdC1x+9HelzKHVUgnrhK medpO3bqiNjZPjN2ky7IVVaAjV6Euatm12NCUQBA3K0SKlX6AhBCpFNkET16yfEa aZPY8K94TV0KCk/Fpc2HmX55OwvZxdRaGJKBTBVWoDxDuUvnMQfApD/pvM0Pe24g CGVSgTolHVJgStIWjTZZpVfmMXgzVYka6GiKvqVU8GGDDX/xo6A= =Ov2o -----END PGP SIGNATURE-----
--- End Message ---
