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
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. gdb to use thread_get_name to get it indeed.
> On Wed, Jul 10, 2024 a
Sergey Bugaev, le mer. 10 juil. 2024 21:07:21 +0300, a ecrit:
> in general, what's this useful for? Debugging, maybe?
Yes, but also because we see more and more software assuming that these
functions are available... (just because they are on Linux)
Samuel
Hi Flavio,
in general, what's this useful for? Debugging, maybe?
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?
On Wed, Jul 10, 2024 at 7:04 PM Flavio Cruz wrote:
> diff --git a/htl/pt-internal.h b/
Some notable differences with Linux:
- We are not inheriting the program name.
- The name can be up to 64 chars (versus Linux's 16).
Also added a mach_RPC_CHECK to check for the existing of gnumach RPCs.
---
config.h.in | 3 +
htl/Makefile
