On Fri, Jan 3, 2025 at 5:32 AM Zhaoming Luo wrote:
> > in the latter case, you should get MIG_BAD_ID from the kernel, so you
> > can detect that.
> What's the best way to handle the MIG_BAD_ID case. I tried perror(NULL)
> but it gave my output '(ipc/mig) bad request message ID'. To be honest I
> d
On 1/1/25 5:50 PM, Sergey Bugaev wrote:
Happy New Year!
Happy New Year
On Wed, Jan 1, 2025 at 12:25 PM Zhaoming Luo wrote:
---
sysdeps/mach/clock_gettime.c | 12
1 file changed, 12 insertions(+)
diff --git a/sysdeps/mach/clock_gettime.c b/sysdeps/mach/clock_gettime.c
index
Hello,
Sergey Bugaev, le mer. 01 janv. 2025 12:50:48 +0300, a ecrit:
> On Wed, Jan 1, 2025 at 12:25 PM Zhaoming Luo wrote:
> >
> > ---
> > sysdeps/mach/clock_gettime.c | 12
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/sysdeps/mach/clock_gettime.c b/sysdeps/mach/clock_g
Zhaoming Luo, le mer. 01 janv. 2025 18:04:16 +0800, a ecrit:
> On 1/1/25 5:51 PM, Zhaoming Luo wrote:
> > ---
> > sysdeps/mach/clock_gettime.c | 12
> > 1 file changed, 12 insertions(+)
> The website[0] mentions making `gettimeofday()` use the CLOCK_MONOTONIC.
Mmm, that website com
On 1/1/25 5:51 PM, Zhaoming Luo wrote:
---
sysdeps/mach/clock_gettime.c | 12
1 file changed, 12 insertions(+)
The website[0] mentions making `gettimeofday()` use the CLOCK_MONOTONIC.
Does that refer to this one[1]?
[0]: https://darnassus.sceen.net/~hurd-web/open_issues/clock_g
Happy New Year!
On Wed, Jan 1, 2025 at 12:25 PM Zhaoming Luo wrote:
>
> ---
> sysdeps/mach/clock_gettime.c | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/sysdeps/mach/clock_gettime.c b/sysdeps/mach/clock_gettime.c
> index 6fffad39f5..22faf85730 100644
> --- a/sysdeps/mach
