reporting this issue niri-wm/niri#3523 (comment) i ran niri under lurk.
it did, as far as i can tell, correctly trace the syscalls, but also printed
"Invalid syscall number 18446744073709551615" to stderr.
now i am not actually experiencing any issues, but i would like to know how that happens, can you give any advice on how to find where that came from?