---
include/mach/gnumach.defs | 8
kern/thread.c | 21 +
2 files changed, 29 insertions(+)
diff --git a/include/mach/gnumach.defs b/include/mach/gnumach.defs
index 7ecf74d..f13e866 100644
--- a/include/mach/gnumach.defs
+++ b/include/mach/gnumach.defs
@@
We use thread_get_name and thread_set_name to get and set the thread
name, so nothing is stored in the thread structure since these functions
are supposed to be called sparingly.
One notable difference with Linux is that the thread name is up to 32
chars, whereas Linux's is 16.
Also added a mach_
On Wed, Jul 10, 2024 at 9:31 PM Samuel Thibault
wrote:
> Sergey Bugaev, le mer. 10 juil. 2024 21:07:21 +0300, a ecrit:
> > Do you expect the process itself to query its threads' names locally,
> > or do you expect another process (GDB) to issue thread_get_name
> > remotely?
>
> We'll want e.g. gd