public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/28598] 5.0 test failures on hppa-linux-gnu
Date: Wed, 17 Nov 2021 20:07:40 +0000	[thread overview]
Message-ID: <bug-28598-13298-JFa3iFstFw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28598-13298@http.sourceware.org/bugzilla/>

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

--- Comment #2 from dave.anglin at bell dot net ---
The attached change fixes the test fails.

Dave

On 2021-11-17 1:28 p.m., mark at klomp dot org wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=28598
>
> Mark Wielaard <mark at klomp dot org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |mark at klomp dot org
>
> --- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
> The issue here is that debugedit doesn't know about hppa ELF relocations (as
> used in debug sections). See tools/debugedit.c (setup_relbuf):
>
>        rtype = ELF64_R_TYPE (rela.r_info);
>        switch (dso->ehdr.e_machine)
>          {
>          case EM_SPARC:
>          case EM_SPARC32PLUS:
>          case EM_SPARCV9:
>            if (rtype != R_SPARC_32 && rtype != R_SPARC_UA32)
>              goto fail;
>            break;
>          case EM_386:
>            if (rtype != R_386_32)
>              goto fail;
>            break;
>          case EM_PPC:
>          case EM_PPC64:
>            if (rtype != R_PPC_ADDR32 && rtype != R_PPC_UADDR32)
>              goto fail;
>            break;
>          case EM_S390:
>            if (rtype != R_390_32)
>              goto fail;
>            break;
>          case EM_IA_64:
>            if (rtype != R_IA64_SECREL32LSB)
>              goto fail;
>            break;
>          case EM_X86_64:
>            if (rtype != R_X86_64_32)
>              goto fail;
>            break;
>          case EM_ALPHA:
>            if (rtype != R_ALPHA_REFLONG)
>              goto fail;
>            break;
> #if defined(EM_AARCH64) && defined(R_AARCH64_ABS32)
>          case EM_AARCH64:
>            if (rtype != R_AARCH64_ABS32)
>              goto fail;
>            break;
> #endif
>          case EM_68K:
>            if (rtype != R_68K_32)
>              goto fail;
>            break;
> #if defined(EM_RISCV) && defined(R_RISCV_32)
>          case EM_RISCV:
>            if (rtype != R_RISCV_32)
>              goto fail;
>            break;
> #endif
> #if defined(EM_MCST_ELBRUS) && defined(R_E2K_32_ABS)
>          case EM_MCST_ELBRUS:
>            if (rtype != R_E2K_32_ABS)
>                    goto fail;
>            break;
> #endif
>          default:
>          fail:
>            error (1, 0, "%s: Unhandled relocation %d at [%d] for %s section",
>                   dso->filename, rtype, ndx, sec->name);
>          }
>

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

  parent reply	other threads:[~2021-11-17 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 15:46 [Bug debugedit/28598] New: 5.0 test failurures " doko at debian dot org
2021-11-17 15:46 ` [Bug debugedit/28598] " doko at debian dot org
2021-11-17 15:52 ` [Bug debugedit/28598] 5.0 test failures " doko at debian dot org
2021-11-17 18:28 ` mark at klomp dot org
2021-11-17 20:07 ` dave.anglin at bell dot net [this message]
2021-11-18 13:26 ` 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-28598-13298-JFa3iFstFw@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).