25 lines · plain
1# Test that we prefer debug_frame over eh_frame unwind plans. They usually2# contain the same information, and we rarely have both kinds of entries for a3# single function. However, in theory the debug_frame plan can be more complete,4# whereas eh_frame is only required to be correct at places where exceptions can5# be thrown.6 7# UNSUPPORTED: system-windows8# XFAIL: system-darwin9# REQUIRES: target-x86_64, native10 11# RUN: %clang_host -g %p/Inputs/call-asm.c %p/Inputs/prefer-debug-over-eh-frame.s -o %t12# RUN: %lldb %t -s %s -o exit | FileCheck %s13 14breakpoint set -n bar15# CHECK: Breakpoint 1: where = {{.*}}`bar16 17process launch18# CHECK: stop reason = breakpoint 1.119 20target modules show-unwind -n foo21# CHECK: Asynchronous (not restricted to call-sites) UnwindPlan is 'DWARF CFI plus augmentation from assembly parsing'22# CHECK: Synchronous (restricted to call-sites) UnwindPlan is 'DWARF CFI'23# CHECK: eh_frame UnwindPlan:24# CHECK: debug_frame UnwindPlan:25