This issue has been moved from a ticket on Developer Community.
[severity:It bothers me. A fix would be nice]
It seems that in a mixed-mode Python/C++ debugging session, while debugging a piece of Python code, stepping into a function whose implementation is in C++, this does not work if the arguments are unpacked into the function call.
Example:
fast_foo(1, 2, 3) # works, I manage to step into the C++ code
args = (1, 2, 3)
fast_foo(*args) # does not work, it instead steps over the function call
A work around seems to be to either set a break point in the C++ code, or to change the calling code:
args = (1, 2, 3)
fast_foo.__call__(*args)
For some reason, using the __call__ method seems to not suffer from the problem. However, both of these work arounds are not really satisfactory.
Original Comments
(no comments)
Original Solutions
(no solutions)
This issue has been moved from a ticket on Developer Community.
[severity:It bothers me. A fix would be nice]
It seems that in a mixed-mode Python/C++ debugging session, while debugging a piece of Python code, stepping into a function whose implementation is in C++, this does not work if the arguments are unpacked into the function call.
Example:
A work around seems to be to either set a break point in the C++ code, or to change the calling code:
For some reason, using the
__call__method seems to not suffer from the problem. However, both of these work arounds are not really satisfactory.Original Comments
(no comments)
Original Solutions
(no solutions)