Bug 621719 - libglib-2.0.so.0.2200.5-gdb.py uses "dir" as a variable, shadowing the "dir" builtin
libglib-2.0.so.0.2200.5-gdb.py uses "dir" as a variable, shadowing the "dir" ...
Product: Fedora
Classification: Fedora
Component: glib2 (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2010-08-05 18:40 EDT by Dave Malcolm
Modified: 2010-12-03 11:39 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 11:39:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 636387 None None None Never

  None (edit)
Description Dave Malcolm 2010-08-05 18:40:47 EDT
Description of problem:
/usr/share/gdb/auto-load/lib/libglib-2.0.so.0.2200.5-gdb.py has this fragment:
  dir = '/usr/share/glib-2.0/gdb'
  if not dir in sys.path:
      sys.path.insert(0, dir)

This assignment to "dir" shadows the "dir" builtin, making it more difficult to
use python interactively within gdb.

Suggest the use of "dir_" instead of "dir"

Version-Release number of selected component (if applicable):

c.f: attempting to debug my gdbheap module:
(gdb) python import gdbheap

(gdb) python dir(gdbheap)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: 'str' object is not callable
Error while executing Python code.

(gdb) python print repr(dir)
Comment 1 Dave Malcolm 2010-08-05 18:43:57 EDT
The (tedious) workaround is to fetch the object back from the __builtin__ module and reassign it to "dir":
(gdb) python import __builtin__
(gdb) python dir = __builtin__.dir
Comment 2 Dave Malcolm 2010-08-05 18:45:03 EDT
Seems to be another one in the analogous "gobject" file
Comment 3 Bug Zapper 2010-11-03 07:13:33 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2010-12-03 07:56:23 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 5 Dave Malcolm 2010-12-03 11:23:09 EST
Still present in:
in glib2-devel-2.24.1-1.fc13.x86_64
Comment 6 Dave Malcolm 2010-12-03 11:39:56 EST
Bug still present in latest upstream git; filed upstream as:

Note You need to log in before you can comment on or make changes to this bug.