Re: [PATCH glibc-2.44] Fix __pthread_timedblock for hurd

On 22/8/26 7:24 am, Samuel Thibault wrote:
> Damien Zammit, le ven. 21 août 2026 08:44:24 +0000, a ecrit:
>> I am getting mach_msg_trap after mach_msg is sent and then a hang, if
>> you look at thread 11 in the previous backtrace.
> But the question is: what was supposed to interrupt your timed block? Is
> the condition of wake-up valid or not? Is the timeout value meaningful?

Assuming mach_msg_trap is from a SIGTRAP? (I cant see the backtrace of 
thread 3 that raised a signal).
The SIGTRAP signal is blocked from the sigmask, would it make a difference
if I added that signal to the sigmask?

Damien