This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients dmalcolm, loewis
Date 2010-04-03.15:45:50
SpamBayes Score 5.9328653e-05
Marked as misclassified No
Message-id <4BB762AC.4020104@v.loewis.de>
In-reply-to <1270309068.18.0.720455881047.issue8279@psf.upfronthosting.co.za>
Content
> What is the output of "gdb --version" on this machine?

GNU gdb (GDB) 7.0.1-debian
This GDB was configured as "x86_64-linux-gnu".

The debian package is 7.0.1-2

> $ gdb --batch --eval-command "python print gdb.Frame.function"
> --eval-command "python print dir(gdb.Frame)"

Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: type object 'gdb.Frame' has no attribute 'function'
Error while executing Python code.
['__class__', '__delattr__', '__doc__', '__eq__', '__ge__',
'__getattribute__', '__gt__', '__hash__', '__init__', '__le__',
'__lt__', '__ne__', '__new__', '__reduce__', '__reduce_ex__',
'__repr__', '__setattr__', '__str__', 'is_valid', 'name', 'newer',
'older', 'pc', 'read_var', 'type', 'unwind_stop_reason']

> The fix would be to detect the presence of gdb.Frame.function, and
> enable/disable the commands and their selftests accordingly, assuming
> that it's OK to add a conditional dependency on code that isn't
> merged into gdb's trunk yet.

That would be fine, I think. Please add a comment saying that gdb 7.0.1
didn't have this feature yet.
History
Date User Action Args
2010-04-03 15:45:52loewissetrecipients: + loewis, dmalcolm
2010-04-03 15:45:50loewislinkissue8279 messages
2010-04-03 15:45:50loewiscreate