From: Kurt Roeckx <kurt@roeckx.be>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Dwarf unwind test failures on various arches
Date: Tue, 22 Apr 2014 18:14:36 +0200 [thread overview]
Message-ID: <20140422161436.GA32061@roeckx.be> (raw)
In-Reply-To: 1398167143.29199.167.camel@bordewijk.wildebeest.org
[-- Attachment #1: Type: text/plain, Size: 2922 bytes --]
On Tue, Apr 22, 2014 at 01:45:43PM +0200, Mark Wielaard wrote:
> On Mon, 2014-04-21 at 23:40 +0200, Kurt Roeckx wrote:
> > I'm seeing various test suite failures in the 0.158 on various
> > arches. I'm currently looing at powerpc since that's the only
> > Debian release architecture that's having the problem, but I see
> > it on various non-release arches too.
>
> Thanks for the report. It would be nice if you could always output the
> test-suite.log file if the tests fail so they are available in the
> build.log. I did that in the fedora package:
> make -s %{?_smp_mflags} check || (cat tests/test-suite.log; %{nocheck})
I'll add something like that, if I don't forget.
> One question, is this traditional big endian ppc or the new ELFv2 ABI
> ppc64-le architecture? elfutils currently doesn't have a backend for the
> new ELFv2 ABI. It will detect that the ELF files are little endian, but
> it won't know about the other ELFv2 changes (no function descriptors,
> different calling conventions, etc.)
It's the a 32 bit big endian powerpc, I assume it's the ABI that
has existed for over 10 years.
> > FAIL: run-backtrace-native.sh
> > =============================
> >
> > 0x100000 0x103000 [vdso: 14111]
> > 0x20474000 0x20601000 /lib/powerpc-linux-gnu/libc-2.18.so
> > 0x20614000 0x2063d000 /lib/powerpc-linux-gnu/libpthread-2.18.so
> > 0x2064f000 0x20662000 /home/kroeckx/elfutils-0.158/tests/backtrace-child
> > 0x40000000 0x40033000 /lib/powerpc-linux-gnu/ld-2.18.so
> > TID 14111:
> > # 0 0x20626810 raise
> > TID 14112:
> > # 0 0x20626810 raise
> > /home/kroeckx/elfutils-0.158/tests/backtrace: dwfl_thread_getframes: No DWARF information found
> > /home/kroeckx/elfutils-0.158/tests/backtrace: dwfl_thread_getframes: No DWARF information found
> > backtrace: backtrace.c:68: callback_verify: Assertion `seen_main' failed.
> > ./test-subr.sh: line 84: 14110 Aborted (core dumped) LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" $VALGRIND_CMD "$@"
> > backtrace-child: no main
>
> That is strange. It is as if libpthread-2.18.so doesn't have .eh_frame
> available. Could you check?
It does have an .eh_frame
> > FAIL: run-backtrace-dwarf.sh
> > ============================
> >
> > 0xfdf8e08 raise
> > /home/kroeckx/elfutils-0.158/tests/backtrace-dwarf: dwfl_thread_getframes: No DWARF information found
> > dwarf: no main
> > rmdir: failed to remove 'test-14137': Directory not empty
>
> This is probably similar.
>
> Note that Mathias Klose did find a test issues right after 0.158 was
> released that improved the tests in some cases detecting support wasn't
> really available. See commit e922ec.
I know about it, he talked to me to find out what the problem was.
The patch has been applied.
Kurt
next reply other threads:[~2014-04-22 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 16:14 Kurt Roeckx [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-22 11:45 Mark Wielaard
2014-04-21 21:40 Kurt Roeckx
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=20140422161436.GA32061@roeckx.be \
--to=kurt@roeckx.be \
--cc=elfutils-devel@lists.fedorahosted.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).