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 vstinner
Recipients dmalcolm, loewis, ncoghlan, vstinner
Date 2010-04-19.22:26:28
SpamBayes Score 0.00010397938
Marked as misclassified No
Message-id <1271715991.45.0.968346538097.issue8437@psf.upfronthosting.co.za>
In-reply-to
Content
> (A) that we shouldn't use gdb.Frame.function.name(), ...
> that this was fixed in trunk in r80156.

This command is not correct: it still calls .function() method:
     def is_evalframeex(self):
        '''Is this a PyEval_EvalFrameEx frame?'''
        if self._gdbframe.function():
            if self._gdbframe.name() == 'PyEval_EvalFrameEx':

Call to self._gdbframe.function() can be removed.

> The "py-up" and "py-down" commands and their selftest
> (StackNavigationTests) are made conditional upon this.

It's not enough, test_print_after_up() and test_locals_after_up() require also py-up command.

Attached patch is based on add-conditions-for-gdb.Frame.select-to-trunk.patch and fix described problems. Using test_gdb-2.patch, test_gdb pass without any error on my Debian Sid (gdb 7.1).
History
Date User Action Args
2010-04-19 22:26:31vstinnersetrecipients: + vstinner, loewis, ncoghlan, dmalcolm
2010-04-19 22:26:31vstinnersetmessageid: <1271715991.45.0.968346538097.issue8437@psf.upfronthosting.co.za>
2010-04-19 22:26:30vstinnerlinkissue8437 messages
2010-04-19 22:26:30vstinnercreate