** Expected results on x86 Linux
The following tests are expected to fail on x86 Linux:
Gtest-bt (see http://sources.redhat.com/bugzilla/show_bug.cgi?id=595)
Ltest-bt (likewise)
Gtest-resume-sig (likewise)
Ltest-resume-sig (likewise)
Gtest-dyn1 (no dynamic unwind info support yet)
Ltest-dyn1 (no dynamic unwind info support yet)
test-setjmp (longjmp() not implemented yet)
run-check-namespace (no _Ux86_getcontext yet)
So, indeed, x86 tests are expected to fail and according to the README,
a lot of the same ones fail for x86_64.
The first major feature we are trying to implement for Frysk using
libunwind will be to get backtraces, so, if you want some focus on where
to place development resources, that is the initial area we will be
concentrating on. Remote debugging is definitely in our plans, but is
not our immediate goal. We want to get local debugging solid before
moving on to remote deugging. Any changes you make should be flexible
enough to be able to handle remote debugging in the future.
Hope this helps.