Your message dated Mon, 8 Jul 2024 14:30:28 +0200
with message-id <Zovb5F0UuV3Jmz1q@per>
and subject line gdb: symbols fixed
has caused the Debian Bug report #1070699,
regarding gdb can not be started on testing
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.)
--
1070699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070699
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdb
Version: 13.2-1+b1
Severity: grave
Justification: renders package unusable
mmediately stops with the error:
gdb: symbol lookup error: /lib/x86_64-linux-gnu/libpython3.11.so.1.0: undefined
symbol: XML_SetReparseDeferralEnabled
libpython3.11.so.1.0 is part of libpython3.11t64
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gdb depends on:
ii libbabeltrace1 1.5.11-3+b6
ii libc6 2.38-7
ii libdebuginfod1t64 0.191-1+b1
ii libexpat1 2.6.2-1
ii libgcc-s1 14-20240330-1
ii libgmp10 2:6.3.0+dfsg-2+b1
ii libipt2 2.0.6-1
ii liblzma5 5.6.1+really5.4.5-1
ii libmpfr6 4.2.1-1+b1
ii libncursesw6 6.4+20240414-1
ii libpython3.11t64 3.11.9-1
ii libreadline8t64 8.2-4
ii libsource-highlight4t64 3.1.9-4.3
ii libstdc++6 14-20240330-1
ii libtinfo6 6.4+20240414-1
ii libxxhash0 0.8.2-2+b1
ii libzstd1 1.5.5+dfsg2-2
ii zlib1g 1:1.3.dfsg-3.1
Versions of packages gdb recommends:
ii libc6-dbg [libc-dbg] 2.38-7
Versions of packages gdb suggests:
pn gdb-doc <none>
pn gdbserver <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 gdb/13.2-1+b2
In the meantime gdb was rebuilt for python3.12, and the problem
apparently has vanished.
--- End Message ---
