From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: Running libunwind tests (--enable-check-libunwind)
Date: Mon, 08 Oct 2007 09:16:00 -0000 [thread overview]
Message-ID: <1191834973.3859.8.camel@dijkstra.wildebeest.org> (raw)
Hi,
There is a new configure option --enable-check-libunwind that builds the
embedded frysk libunwind testsuite and lets make check run it, but not
for the cross-architecture versions of libunwind that we build (they are
build with different flags so results aren't comparable in that case).
This is handy for doing a sanity check of our copy of libunwind, that
still contains a couple of patches not upstream yet. The results aren't
very great (but neither is the upstream version, we are currently a
little better because we have some additional tests not yet upstream),
see the libunwind/README for the "known to fail" (sigh) tests. They are
still useful for general platform checks since it will catch some cases
where the platform vdso or glibc are missing proper CFI information. So
maybe it makes sense to enable them on the autobuilder/tester just as
reference. Otherwise you would only use this as sanity check when
merging/importing new libunwind versions.
Cheers,
Mark
reply other threads:[~2007-10-08 9:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1191834973.3859.8.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).