Step into from Python to C++ doesn't work if arguments are unpacked into function call #7981
Replies: 3 comments
-
Likely due to code not keeping up with various possible step-in code flows in newer versions of Python. |
Beta Was this translation helpful? Give feedback.
-
Relevant code parts: PTVS/Python/Product/Debugger.Concord/TraceManagerLocalHelper.cs Lines 220 to 223 in 421d001 PTVS/Python/Product/Debugger.Concord/TraceManagerLocalHelper.cs Lines 539 to 813 in 421d001 So basically there's some code path that handles the |
Beta Was this translation helpful? Give feedback.
-
Thank you for your report! While we recognize this bug is a limitation, due to our limited resources, we may not be able to prioritize this in the near term. We are going to move this to discussion and give the community 60 days to provide 7 👍 upvotes to gauge general interest. If there's enough upvotes then we will consider incorporating this in an upcoming sprint. If there's unfortunately not enough upvotes then we will close this issue. Thanks! |
Beta Was this translation helpful? Give feedback.
-
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)
Beta Was this translation helpful? Give feedback.
All reactions