From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/24000] couple of testsuite fails with uclibc library
Date: Sat, 09 Feb 2019 21:52:00 -0000 [thread overview]
Message-ID: <bug-24000-10460-e985Wljp3z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24000-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24000
--- Comment #8 from Mark Wielaard <mark at klomp dot org> ---
(In reply to selva from comment #6)
> (In reply to Mark Wielaard from comment #5)
> > (In reply to selva from comment #4)
> > > Created attachment 11548 [details]
> > > Uclibc full testsuite log
> > >
> > > Attaching the full test suite log.
> >
> > BTW. It is easier to just attache the tests/test-suite.log.
> > But I am afraid there still isn't enough to figure out what is going wrong.
> > Maybe the config.log could show a bit more.
> >
> > Please run one of the segfaulting tests under gdb and get a backtrace to
> > show what is really going on.
>
> Mmm., Tried to run the test with gdb but i get "no stack" Please share me
> the steps to get the backtrace if you have any.
Best to figure out which of the tests in run-elfputzdata.sh actually fails and
then run that by hand on the failing test file (bunzip2ed first).
e.g.
cp tests/testfile4.bz2 .
bunzip2 testfile4.bz2
LD_LIBRARY_PATH=backends:libelf:libdw gdb --args tests/elfputzdata gnu
testfile4
(gdb) run
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-02-09 21:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 14:12 [Bug general/24000] New: " ksd.selvakumar at yahoo dot in
2019-01-06 21:06 ` [Bug general/24000] " mark at klomp dot org
2019-01-07 8:30 ` ksd.selvakumar at yahoo dot in
2019-01-13 21:22 ` mark at klomp dot org
2019-01-19 8:31 ` ksd.selvakumar at yahoo dot in
2019-01-23 19:46 ` mark at klomp dot org
2019-02-01 9:31 ` ksd.selvakumar at yahoo dot in
2019-02-01 9:35 ` ksd.selvakumar at yahoo dot in
2019-02-09 21:52 ` mark at klomp dot org [this message]
2019-02-09 22:04 ` mark at klomp dot org
2019-02-18 12:09 ` ksd.selvakumar at yahoo dot in
2019-02-18 12:16 ` ksd.selvakumar at yahoo dot in
2019-02-18 18:51 ` mark at klomp dot org
2019-02-18 18:54 ` mark at klomp dot org
2019-02-19 8:00 ` Ulf Hermann
2019-02-19 10:48 ` Symbol versioning (Was: [Bug general/24000] couple of testsuite fails with uclibc library) Mark Wielaard
2019-02-19 11:30 ` Ulf Hermann
2019-02-19 11:53 ` Mark Wielaard
2019-02-18 21:44 ` [Bug general/24000] couple of testsuite fails with uclibc library mark at klomp dot org
2019-02-19 10:40 ` ksd.selvakumar at yahoo dot in
2019-02-19 15:40 ` [Bug general/24000] couple of ELF compression " mark at klomp dot org
2019-02-20 6:04 ` ksd.selvakumar at yahoo dot in
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=bug-24000-10460-e985Wljp3z@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).