Kallsyms: fix detection when first lines are zero
This CL fixes a couple of issues and re-enables the
test on non-cuttlefish:
- The first entries of /proc/kallsyms can be
zero even when kptr_restrict is lowered. Improve
the heuristic for that by looking at the first page.
- make the KernelAddressSymbolization run for longer
and re-enable it. Because the symbolizer is initialized
asynchronously, we need to give time to the traced_probes
process to enqueue the PostTask, before sending the stop.
Othewise traced_probes might end up running, in sequence:
Start, Stop, InitializeSymbolizer.
- Re-enable the KernelAddressSymbolization but not on
cuttlefish. cf on GCE seems too slow and it would hit the
timeout in the production code. Not worth incrementing that
to deal with slow emulators. Our CI is fine because on
standalone builds we don't use the setprop & wait-with-timeout
path but directly lower kptr_restrict.
Test: perfetto_integrationtests
Change-Id: I9e0933d11f25a9b79198cd70927d88d400454a42
diff --git a/Android.bp b/Android.bp
index 9b79fcb..c7ef420 100644
--- a/Android.bp
+++ b/Android.bp
@@ -7404,6 +7404,7 @@
name: "perfetto_src_traced_probes_ftrace_kallsyms_unittests",
srcs: [
"src/traced/probes/ftrace/kallsyms/kernel_symbol_map_unittest.cc",
+ "src/traced/probes/ftrace/kallsyms/lazy_kernel_symbolizer_unittest.cc",
],
}