when i use perfetto heap profiler capture android application native memory, I found there exist some ERRO_UNWIND_INFO call stack, such as following:
Although I have provided so including the complete symbol table,But still there is the above error stack,I checked some information and found that libunwindstack cannot get the complete stack in some cases.
Could the above reasons cause libunwind to fail to expand the stack? In addition, does the rawtrace file still retain a stack with an address for the ErrorUnwindInfo part? If so, how do I get this part of the address?
Thank you !