Issue 37090: test_gdb's test_pycfunction should test all calling conventions - Python tracker

➜

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.

classification
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: petr.viktorin Nosy List: petr.viktorin
Priority: normal Keywords: patch

Created on 2019-05-29 21:38 by petr.viktorin, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 13668 merged petr.viktorin, 2019-05-29 21:46
Messages (2)
msg343927 - (view) Author: Petr Viktorin (petr.viktorin) * (Python committer) Date: 2019-05-29 21:38 
test_gdb.StackNavigationTests.test_pycfunction checks that the GDB integration can pick up calls to C-API functions. Currently it includes the comment:

> Tested function must not be defined with METH_NOARGS or METH_O,
> otherwise call_function() doesn't call PyCFunction_Call()

This is (now?) false; furthermore it looks like all builtin_function_or_method are discoverable.

As the code paths for various METH_* conventions are diverging due to optimizations, we should check they continue to be covered.
msg352181 - (view) Author: Petr Viktorin (petr.viktorin) * (Python committer) Date: 2019-09-12 14:38 
Fixed here and in https://bugs.python.org/issue37499 ( https://github.com/python/cpython/pull/15776 )