SIGUSR1 in clock_nanosleep()? how to isolate this issue?

[Sebastiaan Koppe]

On Thursday, 20 August 2020 at 18:58:43 UTC, mw wrote:
> Hi,
>
> I run into an issue: it's SIGUSR1 in clock_nanosleep()
>
> [...]
> 
> Anyone has some suggestions on how to isolate this issue?
>
> Thanks.

Try "handle SIGUSR1 nostop noprint" and "handle SIGUSR2 nostop 
noprint" in gdb.