public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "jose.marchesi at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/23732] Test failures on sparc64-linux-gnu
Date: Wed, 03 Oct 2018 12:33:00 -0000	[thread overview]
Message-ID: <bug-23732-10460-30iSpTfN2h@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23732-10460@http.sourceware.org/bugzilla/>

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

Jose E. Marchesi <jose.marchesi at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2018-10-03
                 CC|                            |jose.marchesi at oracle dot com
           Assignee|unassigned at sourceware dot org   |jose.marchesi at oracle dot com
     Ever confirmed|0                           |1

--- Comment #1 from Jose E. Marchesi <jose.marchesi at oracle dot com> ---
Hi Frank.

Of the failures you report, I can only reproduce the failure in
run-strip-nothing.sh.  Looking at it.

Regarding the failure in the backtrack, it is probably due to the fact the
debugging information for glibc is not available in your system.

Salud!

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

  reply	other threads:[~2018-10-03 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 16:50 [Bug general/23732] New: " kelledin at gmail dot com
2018-10-03 12:33 ` jose.marchesi at oracle dot com [this message]
2018-10-04 10:19 ` [Bug general/23732] " jose.marchesi at oracle dot com
2023-01-14 17:13 ` sam at gentoo dot org
2023-01-18 14:41 ` sam at gentoo dot org

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-23732-10460-30iSpTfN2h@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).