Avoid using thread cache in unwinder.
Using thread cache will cause SIGSEGV for 32bit+kernel4.9 device.
Bug: 190579082
Bug: 189803009
Test: run cts -m CtsSeccompHostTestCases
Change-Id: I47b13d02674aadbacd8dac36d8382eed0885413c
Merged-In: I47b13d02674aadbacd8dac36d8382eed0885413c
Signed-off-by: yidong zhang <yidong.zhang@amlogic.com>
(cherry picked from commit cbf7c466e6
)
This commit is contained in:
parent
91b351ea7b
commit
72d0f9b6e7
1 changed files with 3 additions and 0 deletions
|
@ -593,6 +593,9 @@ void engrave_tombstone_ucontext(int tombstone_fd, int proto_fd, uint64_t abort_m
|
|||
};
|
||||
|
||||
unwindstack::UnwinderFromPid unwinder(kMaxFrames, pid, unwindstack::Regs::CurrentArch());
|
||||
auto process_memory =
|
||||
unwindstack::Memory::CreateProcessMemoryCached(getpid());
|
||||
unwinder.SetProcessMemory(process_memory);
|
||||
if (!unwinder.Init()) {
|
||||
async_safe_fatal("failed to init unwinder object");
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue