Avoid unexpected log message on BPF program load error

bcc: add lru_hash and lru_percpu_hash map types

profile: -p should match user PID

tcplife: reorder logic to catch missed timestamps

hello_perf_output: match the data type of pid

Signed-off-by: Gary Lin <glin@suse.com>

Remove debug flag override in bcc_exception.h

Clean up bcc_exception.h

biotop.py: fix compiler error on newer kernels

Determine kernel dirs at runtime (fix #743)

Add LLVMCoroutines lib for llvm>=4.0 builds

As some module build directories split headers between `source/` and
`build/` and this varies between distributions, determine the location
at runtime.

Building bcc against a tip of tree llvm introduces a new link failure,
which is fixed by linking against libLLVMCoroutines (which only exists
in 4.0).
Signed-off-by: Brenden Blanco <bblanco@plumgrid.com>

Improve the structure of exception related header files

tcplife.py: Catch passive closed by server, #788

C++ helper class for BCC

* Eliminate rpmlint errors and allow bcc srpm to build on Fedora koji build system

The nightly bcc srpm does not build as-is on Fedora 24. To get the
build to work the following changes were made in the bcc.spec file:

-Specify where to find luajit headers and libraries
-Correctly limit the build to the x86_64 architecture
-Add needed build requires so the srpm can build on Fedora koji
-Run ldconfig so shared library information is updated
-Follow spec conventions by putting %changelog at the end of the spec file

* Further refine the bcc.spec file

Make the following improvements to the gcc.spec file:

-Use local_clang_static variable to allow building with locally installed clang
-Adjust build requires to include nucurses-devel and make
-Put the subpackage descriptions and file list in a more logical order
-Correct the binary rpm dependencies for the subpackages

Fixup test errors in clang, c api

Some errors seem to have cropped up due to updating kernels and clang
library versions.
1. test_c_api fails on kernels (seen on fedora 4.9) where startup_64
doesn't start at a particular address. Simplify the test to hopefully
work in more systems.
2. The lua and python test_clang did a dereference on a particular bio
field, which has been removed. Pick a different field that is more
uniquitous.
3. test_xlate1 was generating code where the verified pointer spilled.
Rewrite the example to store the result on the stack.
Signed-off-by: Brenden Blanco <bblanco@plumgrid.com>

trace: Avoid passing -1 as the pid to USDT