public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "lordheavym at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/22083] New: run-strip-strmerge.sh test fail on i686
Date: Mon, 04 Sep 2017 16:15:00 -0000	[thread overview]
Message-ID: <bug-22083-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=22083

            Bug ID: 22083
           Summary: run-strip-strmerge.sh test fail on i686
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libelf
          Assignee: unassigned at sourceware dot org
          Reporter: lordheavym at gmail dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

* elfutils-0.170
* glibc 2.26
* gcc 7.2.0

----test-suite.log----
==========================================
   elfutils 0.170: tests/test-suite.log
==========================================

# TOTAL: 174
# PASS:  169
# SKIP:  4
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: run-strip-strmerge.sh
===========================

elflint /build/elfutils/src/elfutils-0.170/tests/elfstrmerge
No errors
elfstrmerge
elflint merged.elf
No errors
strip
elflint merged.elf.stripped
No errors
elflint merged.elf.debug
No errors
unstrip
elflint remerged.elf
No errors
elfcmp
elflint /build/elfutils/src/elfutils-0.170/tests/elfstrmerge.o
No errors
elfstrmerge
elflint merged.elf
No errors
strip
elflint merged.elf.stripped
No errors
elflint merged.elf.debug
No errors
unstrip
/build/elfutils/src/elfutils-0.170/src/unstrip: invalid string offset in symbol
[1]
FAIL run-strip-strmerge.sh (exit status: 1)

SKIP: run-backtrace-data.sh
===========================

/build/elfutils/src/elfutils-0.170/tests/backtrace-data: Unwinding not
supported for this architecture
data: arch not supported
SKIP run-backtrace-data.sh (exit status: 77)

SKIP: run-backtrace-native-biarch.sh
====================================

biarch testing disabled
SKIP run-backtrace-native-biarch.sh (exit status: 77)

SKIP: run-backtrace-native-core.sh
==================================

No core.14739 file generated
SKIP run-backtrace-native-core.sh (exit status: 77)

SKIP: run-backtrace-native-core-biarch.sh
=========================================

biarch testing disabled
SKIP run-backtrace-native-core-biarch.sh (exit status: 77)

-------------------------

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-09-04 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 16:15 lordheavym at gmail dot com [this message]
2017-09-04 17:57 ` [Bug libelf/22083] " mark at klomp dot org
2017-09-04 18:35 ` lordheavym at gmail dot com
2017-09-04 21:13 ` mark at klomp dot org
2017-09-19  6:19 ` lordheavym at gmail dot com
2017-09-19 13:51 ` mark at klomp dot org
2017-10-15 14:41 ` lordheavym at gmail dot com
2017-10-15 14:47 ` lordheavym at gmail dot com
2017-10-15 14:50 ` lordheavym at gmail dot com

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-22083-10460@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).