warnings from backtrace

Gary E. Miller gem at rellim.com
Fri Jun 2 03:45:59 UTC 2017

Yo Hal!

On Thu, 01 Jun 2017 20:36:42 -0700
Hal Murray <hmurray at megapathdsl.net> wrote:

> > Hmm, looks to me like it should have compiled, then failed due to
> > missing -lexecinfo.  Can you confirm you have
> > HAVE_BACKTRACE_SYMBOLS_FD in your build/config.h?  And configured
> > with --enable-seccomp?   
> It's a BSD box, not Linux, so no seccomp.

Uh, no.  My email example was clearly for seccomp.  Only.  Nothing else
is hooked up to seccomp yet.  My recent emails on assert() go into
details why backtrace is only for seccomp now.

So, back on the original subject of seccomp, did the seccomp
changes work for you?  No point testing seccomp on *BSD.

> But we want the backtrace for other than seccomp, right?

Want, yes.  Have, no.  The assert() needs fixing before more 
calls to backtrace beyond seccomp.

> From grep BACK config.h
> #define USEBACKTRACE 1

Well, that is bad a different way.  You say you have execinto.h, but
waf did not find it.

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/20170601/50994eec/attachment.bin>

More information about the devel mailing list