gdb/dap - Getting thread names
authorSimon Farre <simon.farre.cx@gmail.com>
Mon, 12 Jun 2023 19:32:46 +0000 (21:32 +0200)
committerSimon Farre <simon.farre.cx@gmail.com>
Mon, 19 Jun 2023 14:08:45 +0000 (16:08 +0200)
commitf1a614dc8f015743e9fe7fe5f3f019303f8db718
tree2a30f02a32985a317ab4993b7bde815361fd2ba2
parent74d39f70cd9090ba1cdc406421480bb50a864cd2
gdb/dap - Getting thread names

Renamed thread_name according to convention (_ first)

When testing firefox tests, it is apparent that
_get_threads returns threads with name field = None.

I had initially thought that this was due to Firefox setting the names
using /proc/pid/task/tid/comm, by writing directly to the proc fs the
names, but apparently GDB seems to catch this, because I re-wrote
the basic-dap.exp/c to do this specifically and it saw the changes.

So I couldn't determine right now, what operation of name change that
GDB does not pick up, but with this patch, GDB will pick up the thread
names for an applications that set the name of a thread in ways that
aren't obvious.
gdb/python/lib/gdb/dap/threads.py