[issue46649] Propagate Python thread name to thread state structure

2022-02-05 Thread Oleg Iarygin
Oleg Iarygin added the comment: > bpo-15500 looks like a more generic option, debuggers should be able to > retrieve thread names. That option is not viable. 1. > Created on 2012-07-30 16:19 by bra, last changed 2022-01-19 00:32 by pitrou 2. > I don't think this should be done by default as

[issue46649] Propagate Python thread name to thread state structure

2022-02-05 Thread Gabriele N Tornetta
Gabriele N Tornetta added the comment: Thanks for mentioning that issue, it didn't come up in my search for a similar one. Indeed, with the proposals in bpo-15500 implemented, and the fact that native_thread_id is already in PyThreadState, retrieving the name should be easy and might make fo

[issue46649] Propagate Python thread name to thread state structure

2022-02-05 Thread STINNER Victor
STINNER Victor added the comment: bpo-15500 looks like a more generic option, debuggers should be able to retrieve thread names. faulthandler dumps "tstate->thread_id", maybe it should also dump "tstate->native_thread_id" and/or the thread name. -- nosy: +vstinner _

[issue46649] Propagate Python thread name to thread state structure

2022-02-05 Thread Gabriele N Tornetta
Change by Gabriele N Tornetta : -- keywords: +patch pull_requests: +29319 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31142 ___ Python tracker

[issue46649] Propagate Python thread name to thread state structure

2022-02-05 Thread Gabriele N Tornetta
New submission from Gabriele N Tornetta : For tools like Austin (https://github.com/P403n1x87/austin) it is currently quite challenging to derive the name of a thread based on the information exposed by the PyThreadState structure and one stored in threading._active. I would like to propose p