platform_system_core/debuggerd/handler
Christopher Ferris b999b82eb7 Dump threads in tombstone fallback path.
When dumping a tombstone using the fallback path, only the main
thread was showing up. Modify the code to dump the threads using
a slightly different path for the tombstone generation code.

In addition, while looking at this code, two MTE variables were
not set in the tombstone fallback code. Added those variables
so MTE devices will work properly in this fallback path.

Modified the tombstone unit tests for seccomp to have
multiple threads and verify those threads show up in the tombstone.

Bug: 208933016

Test: Ran unit tests.
Test: Ran debuggerd <PID> on a privileged process and verified
Test: all threads dumped. Also verified that the tagged_addr_ctrl
Test: variable is present on the raven device.
Change-Id: I16eadb0cc2c37a7dbc5cac16af9b5051008b5127
2022-02-16 15:02:38 -08:00
..
debuggerd_fallback.cpp Dump threads in tombstone fallback path. 2022-02-16 15:02:38 -08:00
debuggerd_fallback_nop.cpp debuggerd: unify licenses. 2021-06-18 15:49:30 -07:00
debuggerd_handler.cpp Always use main thread pid for manual dumping. 2021-07-30 14:08:03 -07:00
fallback.h Fix multithreaded backtraces for seccomp processes. 2018-09-12 18:12:13 -07:00