From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/23903] Uses linux specifc mremap
Date: Fri, 09 Aug 2019 21:19:00 -0000 [thread overview]
Message-ID: <bug-23903-10460-0iSJmxUquY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23903-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23903
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-08-09
Assignee|unassigned at sourceware dot org |mark at klomp dot org
Ever confirmed|0 |1
--- Comment #13 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Jean Michault from comment #12)
> I propose another patch that checks mremap.
That looks perfectly reasonable. Thanks.
It isn't really necessary for such small patches, but would you mind taking a
look at our CONTRIBUTING file and let me know if you are OK with your
Signed-off-by for this patch?
https://sourceware.org/git/?p=elfutils.git;a=blob_plain;f=CONTRIBUTING;hb=HEAD
> I tested on a debian system GNU / Hurd 2019. The compilation is going well
> but some tests fail:
>
> ============================================================================
> Testsuite summary for elfutils 0.176
> ============================================================================
> # TOTAL: 205
> # PASS: 170
> # SKIP: 23
> # XFAIL: 0
> # FAIL: 12
> # XPASS: 0
> # ERROR: 0
>
> failing tests are :
> FAIL: run-readelf-loc.sh
> FAIL: run-readelf-ranges.sh
> FAIL: run-bug1-test.sh
> FAIL: run-varlocs.sh
> FAIL: run-allfcts-multi.sh
> FAIL: elfstrtab
> FAIL: emptyfile
> FAIL: run-get-units-split.sh
> FAIL: run-attr-integrate-skel.sh
> FAIL: run-all-dwarf-ranges.sh
> FAIL: run-unit-info.sh
> FAIL: run-copyadd-sections.sh
I would expect run-copyadd-sections to fail (because it explicitly tests this
code path and will fail if mremap fails). But some of the others are
surprising. Would you mind attaching the tests/test-suite.log file so we can
inspect how exactly these tests fail?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-09 21:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:28 [Bug libelf/23903] New: " kurt at roeckx dot be
2018-11-21 12:31 ` [Bug libelf/23903] " mark at klomp dot org
2018-11-21 19:21 ` kurt at roeckx dot be
2018-11-21 19:25 ` kurt at roeckx dot be
2018-11-23 9:11 ` mark at klomp dot org
2018-11-23 17:43 ` kurt at roeckx dot be
2018-11-23 20:31 ` mark at klomp dot org
2018-11-23 21:29 ` kurt at roeckx dot be
2019-08-03 20:17 ` bibi584762 at gmail dot com
2019-08-03 20:56 ` mark at klomp dot org
2019-08-04 6:30 ` bibi584762 at gmail dot com
2019-08-04 16:38 ` bibi584762 at gmail dot com
2019-08-04 16:47 ` bibi584762 at gmail dot com
2019-08-09 21:19 ` mark at klomp dot org [this message]
2019-08-26 14:29 ` mark at klomp dot org
2022-07-01 21:25 ` 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-23903-10460-0iSJmxUquY@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).