From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in 0.174 release
Date: Tue, 18 Sep 2018 15:21:00 -0000 [thread overview]
Message-ID: <bug-23673-10460-63reHQCcIU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23673-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23673
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
We reviewed this on irc and came to the surprising conclusion that this was
caused by ptrace TRACEME failing with EPERM. That is really odd. But not a bug
in elfutils IMHO.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-09-18 15:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 10:59 [Bug tools/23673] New: " mliska at suse dot cz
2018-09-17 11:41 ` [Bug tools/23673] " mark at klomp dot org
2018-09-17 11:45 ` mliska at suse dot cz
2018-09-17 19:44 ` mark at klomp dot org
2018-09-18 7:38 ` mliska at suse dot cz
2018-09-18 15:21 ` mark at klomp dot org [this message]
2018-09-19 8:44 ` mliska at suse dot cz
2018-09-19 8:49 ` [Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in at least 0.173 mliska at suse dot cz
2018-09-19 9:29 ` ldv at sourceware dot org
2018-09-19 9:49 ` mliska at suse dot cz
2018-09-19 10:32 ` ldv at sourceware dot org
2018-09-19 10:50 ` mliska at suse dot cz
2018-09-19 11:01 ` ldv at sourceware dot org
2018-09-19 11:09 ` mliska at suse dot cz
2018-09-19 12:44 ` mark at klomp dot org
2018-09-21 8:18 ` mliska at suse dot cz
2018-09-21 9:06 ` mark at klomp dot org
2018-09-21 9:20 ` mliska at suse dot cz
2018-09-21 11:38 ` mark at klomp dot org
2018-10-16 0:13 ` michael.hudson at canonical dot com
2018-10-17 20:41 ` mark at klomp dot org
2018-10-18 2:18 ` michael.hudson at canonical dot com
2018-10-18 6:27 ` mark at klomp dot org
2018-11-16 13:33 ` mliska at suse dot cz
2018-11-16 14:05 ` mark at klomp 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-23673-10460-63reHQCcIU@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).