Re: [Libunwind-devel] [PATCH] testsuite evaluation/fixes for ARM

[Daniel Jacobowitz]

On Thu, Apr 17, 2008 at 03:22:11PM -0400, Bruna Moreira wrote:
> * run-check-namespace:
>     Issue: Some "bashisms" in check-namespace.sh.in causes the script
> to fail to run on N8XX's busybox shell. After fixing those, the test
> still fails because the ARM version of libunwind have _Unwind_*
> interfaces disabled
>     Feature affected: break exceptions completely for ARM [2]

Yes.  Bear in mind that the ARM port only works from DWARF-2 unwind
information.  And unlike other platforms, ARM (post-EABI) does not use
DWARF-2 unwind information for runtime exception handling; there's
no .eh_frame.

So backtraces are about all it's good for.  It would not be a good
choice to use this approach for exceptions.  You can use the normal
ARM EABI exception handling tables for exceptions, but they in turn
are not so good at backtracing.

Adding remote unwind support on the same basis as local support would
not be hard; you mostly have to find a way to tell libunwind where
to find the files.

-- 
Daniel Jacobowitz
CodeSourcery