ISC_PLATFORM_USEBACKTRACE

Gary E. Miller gem at rellim.com
Wed May 31 23:10:11 UTC 2017


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
	gem at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170531/a3f4593a/attachment.bin>


More information about the devel mailing list