Re: [PATCH 3/3] utrace-based ftrace "process" engine, v2

If the full debuginfo is too much, just strip away the sections you don't
need. This can be trivially done [1] when packaging the result.

To trim down the stuff during build, one can give gcc options that limit
the generated amount of debugging. -g implies -g2, maybe -g1 is enough
for SystemTap? From gcc manpage:

"Level 1 produces minimal information, enough for making backtraces in
parts of the program that you don't plan to debug. This includes
dscriptions of functions and external variables, but no information about
local variables and no line numbers."

Gcc has also some other options to constrain the generated debugging
information.

[1]
objcopy -R .debug_info -R .debug_aranges -R .debug_pubnames -R .debug_abbrev -R .debug_line
-R .debug_str -R .debug_ranges -R .comment -R .note ...