Zhaoming Luo, le sam. 22 févr. 2025 21:06:18 +0800, a ecrit: > On Sat, Feb 22, 2025 at 02:01:58PM +0100, Samuel Thibault wrote: > > Zhaoming Luo, le sam. 22 févr. 2025 20:59:53 +0800, a ecrit: > > > On Sat, Feb 22, 2025 at 01:07:40PM +0100, Samuel Thibault wrote: > > > > Zhaoming Luo, le sam. 22 févr. 2025 20:03:12 +0800, a ecrit: > > > > > On Sat, Feb 22, 2025 at 12:47:16PM +0100, Samuel Thibault wrote: > > > > > > Zhaoming Luo, le sam. 22 févr. 2025 19:29:55 +0800, a ecrit: > > > > > > > lib533.c:96 select() failed, with errno 1073741828 (Interrupted > > > > > > > system call) > > > > > > > > > > > > This is expected if the test handles a signal. Does it indeed set > > > > > > up a > > > > > > signal handler and get a signal? > > > > > > > > > > > Eh 'handles a signal' is a bit out of my knowledge, how to confirm > > > > > that? And > > > > > any recommendations reading about the 'signal handler' and 'signal'? > > > > > > > > This is about unix signals. > > > > > > > > Usually gdb already shows their reception when you run the program. > > > > > > > I run it on GNU/Linux. I don't think I see the reception of any signal. > > > > Ok, but does it perhaps do on GNU/Hurd? > > > I don't think so:
Ok. > data > to > lib533.c:100 select() failed, with errno 1073741828 (Interrupted system call) Then it could be coming from pfinet itself, perhaps trace from io_select_common where EINTR is coming from, possibly from signal_pending() which comes from interruptible_sleep_on_timeout setting current->signal = 1;, and then the question is why pthread_hurd_cond_timedwait_np returned EINTR, thus why the condition got canceled. Samuel
