Package: python3.13-dbg Version: 3.13.2-3 Severity: normal $ gdb python3.13 gdb > [ set breakpoint, start Python program ] gdb > py-bt Traceback (most recent call first): (unable to read python frame information) [ repeated ]
This works with Bookworm's python3.11. It also works when I use the python3.13-dbg executable. If this is not easily fixable, the python3.13-gdb.py script should print a message (when it loads!) to the effect that the user should start py3.13-dbg instead of wasting time. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.20-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3.13-dbg depends on: ii libc6 2.41-6 ii libexpat1 2.7.1-1 ii libpython3.13-dbg 3.13.2-3 ii python3.13 3.13.2-3 ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1 Versions of packages python3.13-dbg recommends: ii gdb 16.2-8 Versions of packages python3.13-dbg suggests: pn python3-gdbm-dbg <none> pn python3-tk-dbg <none> -- no debconf information
