gh-143952: Fix asyncio tools to work with the new remote debugging API

[johnslavik]

• Issue: Asyncio debugging tools no longer work (ps and pstree) #143952

[aisk]

Hi, I'm wondering if we can add some tests to ensure we don't break this again in the future?

[johnslavik]

Something's very wrong here. On it.

[johnslavik]

Oh, okay. We have tests for tools but we don't import structures from _remote_debugging. Instead we have our own:

cpython/Lib/test/test_asyncio/test_tools.py

Lines 7 to 11 in 1b52ce8

	FrameInfo=namedtuple('FrameInfo', ['funcname', 'filename', 'lineno'])
	CoroInfo=namedtuple('CoroInfo', ['call_stack', 'task_name'])
	TaskInfo=namedtuple('TaskInfo', ['task_id', 'task_name', 'coroutine_stack', 'awaited_by'])
	AwaitedInfo=namedtuple('AwaitedInfo', ['thread_id', 'awaited_by'])

CC @kumaraditya303

[johnslavik]

OK I guess that's it for the fix itself!

[johnslavik]

We'd want to keep these structures in sync later (we also don't have .opcode in FrameInfo in tests for instance).
I'll check the remote debugging tests in regard to how they manage these structures.

[johnslavik]

OK, it's not a problem. We would just have to pass sequences and we could use original structures.

>>> from _remote_debugging import FrameInfo >>> FrameInfo(range(4)) _remote_debugging.FrameInfo(filename=0, location=1, funcname=2, opcode=3)

[johnslavik]

We'd want to keep these structures in sync later (we also don't have .opcode in FrameInfo in tests for instance). I'll check the remote debugging tests in regard to how they manage these structures.

See GH-143955.

[pablogsal]

Great catch! In retrospective this indeed was doomed to happen so I am glad that we are looking at this