public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/31653] RISC-V: readelf fails to apply R_RISCV_SET/SUB_ULEB128 relocations: [debugedit 5.0] testsuite: 10 11 19 23 failed
Date: Tue, 05 Nov 2024 23:46:59 +0000	[thread overview]
Message-ID: <bug-31653-13298-vxSLG7SGBq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31653-13298@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Mark Wielaard <mark at klomp dot org> ---
(In reply to laokz from comment #6)
> (In reply to Mark Wielaard from comment #5)
> > Luckily it is easy to ignore stderr warnings with AT_CHECK.
> > Could you try the attached patch?
>
> Yes. I tried and it worked! (rebased against our debugedit-5.0 package)

Thanks for testing. Committed as:

commit 785f451a1b05f89c3b24eb5550f35488b80152b7
Author: Mark Wielaard <mark@klomp.org>
Date:   Wed Nov 6 00:28:40 2024 +0100

    tests: Ignore stderr output of readelf in debugedit.at

    readelf might produce some warning messages that don't matter for the
    specific tests in debugedit.at. So ignore stderr output and just check
    stdout output is as expected.

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

    Signed-off-by: Mark Wielaard <mark@klomp.org>

> > If there is no bug yet, we should file a binutils bug against readelf
> > (apply_relocations) should handle R_RISCV_SET_ULEB128 and R_RISCV_SUB_ULEB128
> Indeed.

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

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

      parent reply	other threads:[~2024-11-05 23:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  8:35 [Bug debugedit/31653] New: " akyragvtdizi at gmail dot com
2024-05-15 11:25 ` [Bug debugedit/31653] " mark at klomp dot org
2024-10-30 13:10 ` laokz at foxmail dot com
2024-11-02 19:03 ` mark at klomp dot org
2024-11-03  3:01 ` laokz at foxmail dot com
2024-11-03 16:47 ` mark at klomp dot org
2024-11-04  4:12 ` laokz at foxmail dot com
2024-11-05 23:46 ` mark at klomp dot org
2024-11-05 23:46 ` mark at klomp dot org [this message]

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-31653-13298-vxSLG7SGBq@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=debugedit@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).