Yo Hal! Check out commit 99df9ac91a01a254ca19bbf72d1c2f0fe297d522
It has code to print out the failed syscall #. At least on some OS.
I'll see which fail and then blacklist them. So far it seems to work on
all the buildbot workers. I can't believe that is right...
Notice no need for backtrace(). In fact, I spent some more time
with backtrace(). The failed syscall is never in the backtrace, so
backtrace would be useless here.
AFAIK, the isc_backtrace never did anything useful. BUT, at least
with gcc I see a way to make it useful, I'll get back to that, after
I finish up on your seccomp issue.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpVcGMq56X1C.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
