search for: unwindcursor

...calAddressSpace>::decodeFDE(libunwind::LocalAddressSpace&, unsigned long long, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::FDE_Info*, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::CIE_Info*) + 149 2 libSystem.B.dylib 0x00007fff8719d928 libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::setInfoBasedOnIPRegister(bool) + 312 3 libSystem.B.dylib 0x00007fff8719e348 libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::step() + 216 4 libobjc.A.dylib...

...dressSpace>::decodeFDE(libunwind::LocalAddressSpace&, unsigned long long, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::FDE_Info*, libunwind::CFI_Parser<libunwind::LocalAddressSpace>::CIE_Info*) + 149 > 2 libSystem.B.dylib 0x00007fff8719d928 libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::setInfoBasedOnIPRegister(bool) + 312 > 3 libSystem.B.dylib 0x00007fff8719e348 libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::step() + 216 > 4 libobjc.A.dylib...

Hi All, We recently migrated to llvm 9 from gcc -7 and found that the stack usage is more like 5K in the below function getInfoFromDwarfSection() @ line : 1484 <https://github.com/llvm-mirror/libunwind/blob/master/src/UnwindCursor.hpp#L1484> With our analysis and found that "typename CFI_Parser<A>::PrologInfo prolog" local data is taking up almost 4K space. So we thinking to refactor the code by pushing the "prolog" to a global scope. Any comments on our approach will be appreciated Thank you...

...here extern void *__deregister_frame_info_bases(const void *fde) ^ 18 warnings generated. [8/9] Building CXX object src/CMakeFiles/unwind_shared.dir/libunwind.cpp.obj In file included from C:/Users/clang/libunwind/src/libunwind.cpp:22: In file included from C:/Users/clang/libunwind/src/UnwindCursor.hpp:67: In file included from C:/Users/clang/libunwind/src/CompactUnwinder.hpp:19: C:/Users/clang/libunwind/include\mach-o/compact_unwind_encoding.h:45:5: warning: enumerator value is not representable in the underlying type 'int' [-Wmicrosoft-enum-value] UNWIND_IS_NOT_FUNCTION_START...

...b) bt #0 0x00007fff8d734a81 in libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncodingFrameless () #1 0x00007fff8d73233b in libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncoding () #2 0x00007fff8d7322e1 in libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::step () #3 0x00007fff8d736262 in _Unwind_Backtrace () #4 0x000000010004a17c in SlowUnwindStack () at /Users/glider/src/asan2/llvm/projects/compiler-rt/lib/sanitizer_common/sanitizer_unwind.cc:116 I've inserted a debug printf i...

Hi Nick, It is a pleasure to be in contact with the creator of the compact unwind approach! I can see how an array of 32-bit unwind blocks could be used to describe each distinct point within a function (within a prolog in particular). But then you end up with six or seven or more such blocks for a large percentage of functions, don't you? Seems like a lot of additional space for something