[ python-Bugs-1229680 ] Tracing C function calls and keyword arguments

[SourceForge.net]

Bugs item #1229680, was opened at 2005-06-29 14:00
Message generated for change (Comment added) made by mwh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1229680&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Frank Cieslok (fcieslok)
>Assigned to: Nick Bastin (mondragon)
Summary: Tracing C function calls and keyword arguments

Initial Comment:
When a tracing/profiling function is registered via 

  'PyEval_SetTrace()' or 'PyEval_SetProfile()', 

calling registered C functions should lead to calls of
the tracing function with reason 

  'PyTrace_C_CALL' and 'PyTrace_C_RETURN'.

This does not work if the function call uses keyword
arguments (test case attached) ! 

The reason seems to be that in
'Python/ceval.c:call_function ()' the macro 'C_TRACE'
is used to wrap the calling of build-in functions into
the corresponding calls of the tracing function. This
does not apply if keyword arguments are used, in that
case 'do_call ()' is called directly without being
wrapped into that macro.


----------------------------------------------------------------------

>Comment By: Michael Hudson (mwh)
Date: 2005-06-29 14:52

Message:
Logged In: YES 
user_id=6656

I think this is the right assignment!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1229680&group_id=5470