Message364086
I'd like to, but it only sets the tracing to the currently running thread (the request is for setting the tracing for other threads).
Just for info, the problem I'm solving is that the debugger is multi-threaded, but the user can start the code without any tracing in place, and then, when it gets to an attach to process or a programmatic attach to the debugger, the debugger needs to set the tracing to threads that are already running (and any new thread created afterward) and Python doesn't really have any structure for that in place (so, I'm using the C-API as a workaround to do what PyEval_SetTrace does but targeting any thread). |
|
Date |
User |
Action |
Args |
2020-03-13 12:19:44 | fabioz | set | recipients:
+ fabioz, vstinner |
2020-03-13 12:19:44 | fabioz | set | messageid: <1584101984.81.0.939402077977.issue35370@roundup.psfhosted.org> |
2020-03-13 12:19:44 | fabioz | link | issue35370 messages |
2020-03-13 12:19:44 | fabioz | create | |
|