regenerate examples index
Add some popularity numbers for examples/category links.
whitespace tweak for examples html index
session: don't suppress warnings in dump mode if -vv

Just like how derive_probes() still prints errors in dump mode if -vv is
supplied, we do the same for warnings.
warn about missing kernel symbol table

On some distros (e.g., arch linux), no System.map* file survives the
build process, but there may be ways to fabricate doppelgangers.

* session.cxx (systemtap_session::parse_kernel_functions): Warn if
  none found.
* warning::symbols: new man page
* warning::debuginfo: xref.
PR16956: add "kernel<linux/types.h>" to all nd_syscall.* @cast ops

We can't take blood from stone - dwarf from a kernel whom we are
targeting for non-dwarf processing.  So generate dwarf from the
headers if necessary.
More linux 3.14 porting, sans CONFIG_USER_NS

This time, cover the remaining tapset/runtime stuff.
linux/runtime.h: more CONFIG_USER_NS fallout

Partially unrolling commit 7d35a948401, because on modern kernels
(3.14+), the from_k?id_munged functions are defined as inlines, and
should be used regardless of CONFIG_USER_NS etc.  The buildrun.cxx
exportedness test for from_kuid_munged would fail, triggering our
runtime to use a do-nothing macro instead.

Until a more programmatic way is found for those unidentified older
kernels that have CONFIG_USER_NS but no from_k?id_munged inlines,
for now a user will have to work around the build problem with

  % stap -DSTAP_FAKE_KID_MUNGED
PR16955: improve blacklisting diagnostics

Create a new enum to describe the reason why the function was
blacklisted. In dwarf_query::add_probe_point(), emit a warning if
blacklisted.
PR16955: adapt testsuite

- pr10854.exp: use -w to suppress warnings re. blacklisted functions
- rlimit.exp: ditto
stapprobes.3stap: highlight obsolete nature of kernel.mark probes
eventcount.stp sample: add some more sorting options, config disclosure
linux runtime: switch to vmalloc for context[] element allocation

The new eventcount.stp changes can result in relatively large context
structures (33712 bytes each on f19/x86-64), which the stp_kmalloc
widget can sometimes fail to allocate.  Switching to the numa-aware
vmalloc front-end lets these allocations succeed.

TBD: those contexts shouldn't be that large.
Fix BZ16960 by handling !CONFIG_USER_NS better.

* buildrun.cxx (compile_pass): Convert the from_kuid_munged() test to a
  compile test, instead of an export test.
* runtime/linux/runtime.h: Restore original CONFIG_USER_NS support.
* runtime/linux/autoconf-from_kuid_munged.c: New autoconf test.
Improve BZ16956 by testing nd_syscall tapset without debuginfo.

* testsuite/systemtap.syscall/nd_syscall.exp: Make sure the nd_syscall
  tapset isn't using debuginfo by setting SYSTEMTAP_DEBUGINFO_PATH to
  /dev/null.
nd_syscall.exp: fix SYSTEMTAP_DEBUGINFO_PATH override

This is a follow-up to commit 27ce133. Tcl's exec proc can't handle env
var setting as part of its args:

couldn't execute "SYSTEMTAP_DEBUGINFO_PATH=/dev/null": no such file or
directory
FAIL: testsuite/systemtap.syscall/nd_sys.stp compilation

We need to explicitly manipulate the env array to set the
SYSTEMTAP_DEBUGINFO_PATH and then restore it afterwards if needed.
listing_mode.exp: rename to listing_mode_sanity.exp
listing_mode.exp: new testcase
simplify derived_probe::script_location()

Rather than relying on yucky heuristics, we go the explicit way. The
script_location() function now relies on the new probe_point member
'well_formed', which is true if the probe point represents the 'final'
script-level expression, after wildcard expansion.

Since only each individual probe builder knows what constitutes a
well-formed probe point, it will be up to those to set the 'well_formed'
flag as needed. If the probe point that we want to list is also the
final one, which is the case for many simpler probe points, then no
further work is needed. The following patches modify the appropriate
builders to do just this.
hwbkpt_builder: add well-formed intermediate probe