Bug 1782160 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I just tested with my Intel local build and found that `libobjc.A.dylib`objc_addExceptionHandler` gets hit when I choose "print using the system dialog", but neither `libunwind::UnwindCursor` nor `libunwind::CFI_Parser` gets hit. So none of the `libunwind` code gets exercised by my Intel local build. I'm not sure why.
Revision 1 by
on 
I just tested with my Intel local build and found that `objc_addExceptionHandler` gets hit when I choose "print using the system dialog", but neither `libunwind::UnwindCursor` nor `libunwind::CFI_Parser` gets hit. So none of the `libunwind` code gets exercised by my Intel local build. I'm not sure why.
Revision 2 by
on 
I just tested with my Intel local build and found that `objc_addExceptionHandler` gets hit when I choose "print using the system dialog", but neither `libunwind::UnwindCursor` nor `libunwind::CFI_Parser` gets hit. So none of the `libunwind` code gets exercised by my Intel local build. I'm not sure why.

Edit: Oops, `libunwind::UnwindCursor` *does* get hit. I forgot to change `Registers_arm64` in its definition to `Registers_x86_64`. So it's only `libunwind::CFI_Parser` that doesn't.
Revision 3 by
on 
I just tested with my Intel local build and found that `objc_addExceptionHandler` gets hit when I choose "print using the system dialog", but neither `libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_arm64>::step()` nor `libunwind::CFI_Parser<libunwind::LocalAddressSpace>::decodeFDE()` gets hit. So none of the `libunwind` code gets exercised by my Intel local build. I'm not sure why.

Edit: Oops, `libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::step()` *does* get hit. I forgot to change `Registers_arm64` in its definition to `Registers_x86_64`. So it's only `libunwind::CFI_Parser<libunwind::LocalAddressSpace>::decodeFDE()` that doesn't.
Revision 4 by
on 
I just tested with my Intel local build (in `lldb`) and found that `objc_addExceptionHandler` gets hit when I choose "print using the system dialog", but neither `libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_arm64>::step()` nor `libunwind::CFI_Parser<libunwind::LocalAddressSpace>::decodeFDE()` gets hit. So none of the `libunwind` code gets exercised by my Intel local build. I'm not sure why.

Edit: Oops, `libunwind::UnwindCursor<libunwind::LocalAddressSpace, libunwind::Registers_x86_64>::step()` *does* get hit. I forgot to change `Registers_arm64` in its definition to `Registers_x86_64`. So it's only `libunwind::CFI_Parser<libunwind::LocalAddressSpace>::decodeFDE()` that doesn't.

Back to Bug 1782160 Comment 2