在我的产品代码中有很多协程,它们在处理请求时被卡在未知的位置。我使用Python support extension将gdb附加到进程,但它没有显示进程停滞的协程中的确切行,只显示了主堆栈跟踪。下面是一个最小的例子:
import asyncio
async def hello():
await asyncio.sleep(30)
print('hello world')
asyncio.run(hello())(gdb) py-bt
Traceback (most recent call first):
File "/usr/lib/python3.8/selectors.py", line 468, in select
fd_event_list = self._selector.poll(timeout, max_ev)
File "/usr/lib/python3.8/asyncio/base_events.py", line 2335, in _run_once
File "/usr/lib/python3.8/asyncio/base_events.py", line 826, in run_forever
None, getaddr_func, host, port, family, type, proto, flags)
File "/usr/lib/python3.8/asyncio/base_events.py", line 603, in run_until_complete
self.run_forever()
File "/usr/lib/python3.8/asyncio/runners.py", line 299, in run
File "main.py", line 7, in <module>GDB显示了一个在第7行结束的跟踪,但代码显然卡在了第4行。如何使用嵌套协程来显示更完整的跟踪?
发布于 2021-05-27 19:44:22
您可以使用aiodebug.log_slow_callbacks.enable(0.05)
https://stackoverflow.com/questions/65704785
复制相似问题