gdb embeds python3.3, but support scripts are not compatible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Python |
Fix Released
|
Unknown
|
|||
gdb (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Saucy |
Invalid
|
Undecided
|
Unassigned | ||
python2.7 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Won't Fix
|
Medium
|
Unassigned | ||
python3.3 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
The saucy gdb appears to be linked against libpython3.3.
This results in a conflict when trying to debug python2.7 programs, which use the python2.7-dbg.py scripts from python2.7-dbg. This makes debugging Python programs difficult.
File "/usr/lib/
Py_
SyntaxError: invalid syntax
File "/usr/lib/
Py_
There are also invalid print statements that show up as well.
If these are updated, then the file parses, but `py-bt` fails with:
Error occurred in Python command: global name 'long' is not defined
Updating all of the long() references to int() doesn't work:
Error occurred in Python command: 'gdb.Value' object cannot be interpreted as an integer
Changed in python: | |
status: | Unknown → New |
Changed in gdb (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
status: | Triaged → Invalid |
Changed in python2.7 (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in python3.3 (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gdb (Ubuntu Saucy): | |
status: | New → Invalid |
Changed in python2.7 (Ubuntu Saucy): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in python3.3 (Ubuntu Saucy): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in python: | |
status: | New → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.