Lua's native Number type is a 64-bit double with 52-bit precision, which
was causing rounding errors when storing and working with high-range
memory addresses (namely, addresses from the kernel, which are all in
the `0xffffffff........` range).

To work around this, we've made sure to never call `tonumber` on any
variables that represent memory addresses, and instead continue
operating on them with their native types: LuaJIT can work with the
underlying `uint64_t` type for these values and transparently perform
all kinds of numeric operations.

The only limitation of working with native 64-bit types in LuaJIT is
that they cannot be printed with the language's default `string.format`
API. To give better UX to probe writers, these APIs have been
monkeypatched so the `%p` format specifier will now properly handle
64-bit addresses and print them in an appropriate format.

bcc-lua: build bcc.lua and bcc.o in the build tree

miscellaneous cleanups to C++ and tools/trace

I didn't actually track this one down, but was getting some errors
coming out of kernel header files when perf_events.h was included first.
Move it after some std headers that mask the issue.

BPF programs aren't allowed to attach to these functions since deadlocks
may occur, thus the test would fail since no stack is collected. Use
update_elem to test instead.

The way to do exception printing in python2/3 compatible way is using
sys.exc_info()[0/1].

bcc-lua: switch to quiet by default

use --verbose to turn verbose output
Signed-off-by: Alexei Starovoitov <ast@fb.com>

Fixed tcpv4connect.py broken link on README

Fix for find_symbol method, issue #478

Add support for nixos

Add support for systems using a non-default ("/lib/modules") kernel lib
directory.

migrated gethostlatency to use bpf_perf_event

Standalone Lua tracing tool

get rid of version checks

version checks don't work at all on kernels with backported bpf bits
they also fail when /usr/include/linux/bpf.h doesn't match loaded
kernel.
Fix these issues by embedding bpf.h into libbcc.so and force load it
in clang, so we can remove all version checks and rely on verifier
complaining on unknown function call.
Later patch can make verifier errors less cryptic by converting
'unknown call 12' to strings.

while at it update bpf.h to the latest.
Signed-off-by: Alexei Starovoitov <ast@fb.com>

Bug fix around USDT argument handling for constants

For USDT arguments of the form "-4@$-1", the parsing logic would fail
because it didn't expect the second number (the actual value of the
USDT argument as a constant) to be negative. This is now fixed.

IPv6 strings with an inet6_ntoa