Message 413421 - 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.

Author	smurfix
Recipients	smurfix
Date	2022-02-17.18:08:22
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1645121302.3.0.866413840913.issue46781@roundup.psfhosted.org>
In-reply-to

Content
When tracing/profiling, the "return" event reports the value returned by the exiting function. However, this does not work for C functions. The profiler's "c_return" hook is called with the same C function object as "c_call". This unnecessarily complicates debugging and should be fixed. https://stackoverflow.com/questions/61067303/get-return-value-of-python-builtin-functions-while-tracing

When tracing/profiling, the "return" event reports the value returned by the exiting function.

However, this does not work for C functions. The profiler's "c_return" hook is called with the same C function object as "c_call". This unnecessarily complicates debugging and should be fixed.

https://stackoverflow.com/questions/61067303/get-return-value-of-python-builtin-functions-while-tracing

History
Date	User	Action	Args
2022-02-17 18:08:22	smurfix	set	recipients: + smurfix
2022-02-17 18:08:22	smurfix	set	messageid: <1645121302.3.0.866413840913.issue46781@roundup.psfhosted.org>
2022-02-17 18:08:22	smurfix	link	issue46781 messages
2022-02-17 18:08:22	smurfix	create