traced: bail out if an invalid trigger mode is specified

This is a fix to a subtle binary back-compat issue.
When introducing a new trigger mode, the service will ignore it
and trace indefinitely (Because duration_ms is checked to be 0).
The issue is not as bad as initially though because perfetto_cmd
mitigates this, by enforcing a hard timeout to 60s + trigger_timeout
regardless of the type of the trigger (See comments in b/274931668).

Bug: 274931668
Bug: 260112703
Test: perfetto_unittests --gtest_filter=TracingServiceImplTest.FailOnUnknownTriggerMode
(cherry picked from commit 7f432673ea568e8ab9b7f4ccfe0107a4c5e01e81)
Change-Id: I7993ec7a3604b8ede00b3c29cf29059685af4848
Merged-In: I7993ec7a3604b8ede00b3c29cf29059685af4848
3 files changed
tree: 228363dee9fd2143b689fbce8db12df2f35c4196
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. python/
  13. src/
  14. test/
  15. tools/
  16. ui/
  17. .clang-format
  18. .clang-tidy
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. .style.yapf
  23. Android.bp
  24. Android.bp.extras
  25. BUILD
  26. BUILD.extras
  27. BUILD.gn
  28. CHANGELOG
  29. codereview.settings
  30. DIR_METADATA
  31. heapprofd.rc
  32. LICENSE
  33. meson.build
  34. METADATA
  35. MODULE_LICENSE_APACHE2
  36. OWNERS
  37. perfetto.rc
  38. PerfettoIntegrationTests.xml
  39. PRESUBMIT.py
  40. README.chromium
  41. README.md
  42. TEST_MAPPING
  43. traced_perf.rc
  44. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.