intrigeri: > Control: tag -1 + moreinfo > > Hi Niels, > > [...] > > syscall numbers are architecture dependent, so: what architecture did > you experience this on? >
amd64. > [...] > Once I have this info I'll ping upstream about it, so the > corresponding syscall is allowed (if that's safe) in next release. > > (I can't reproduce this here with torsocks 2.1.0-2 on sid.) > > Cheers, > -- > intrigeri > True, the particular system call seem to have been fixed. However, I can reproduce it with syscall "204" (sched_getaffinity). A particularly exciting case would be "torsocks mplayer" because mplayer apparently does not give up making it an infinite fprintf loop of warnings. Thanks, ~Niels
