Bug#1005326: no-code-sections triggered on non-ELF files

To: 1005326@bugs.debian.org
Cc: duck@duckcorp.org
Subject: Bug#1005326: no-code-sections triggered on non-ELF files
From: Felix Lechner <felix.lechner@lease-up.com>
Date: Fri, 11 Feb 2022 12:51:06 -0800
Message-id: <[🔎] CAFHYt565Z+CwVRUz_UK8=Y=-dHyz7uFU2wXtSP3+qDNz4eLJ6g@mail.gmail.com>
Reply-to: Felix Lechner <felix.lechner@lease-up.com>, 1005326@bugs.debian.org
In-reply-to: <[🔎] 5072c41c3cadf35f6996b0ae01502d65@duckcorp.org>
References: <[🔎] 5072c41c3cadf35f6996b0ae01502d65@duckcorp.org> <[🔎] 5072c41c3cadf35f6996b0ae01502d65@duckcorp.org>

Hi,

On Fri, Feb 11, 2022 at 12:09 PM Marc Dequènes <duck@duckcorp.org> wrote:
>
> Could you consider improving the check?

Yes, I'd like to.

> readelf fails with "readelf: Error: Not an ELF file - it has the wrong
> magic bytes at the start"

I confirmed that Lintian's invocation produces that error for
usr/lib/dxvk/wine64-development/d3d10.dll.a in dxvk, but how can we
tell such archives apart from those that are legitimately broken?

Kind regards
Felix Lechner

Reply to:

Follow-Ups:
- Bug#1005326: no-code-sections triggered on non-ELF files
  - From: Stephen Kitt <skitt@debian.org>

References:
- Bug#1005326: no-code-sections triggered on non-ELF files
  - From: Marc Dequènes (duck) <duck@duckcorp.org>

Prev by Date: Re: Question about a potential false positive error
Next by Date: Re: Question about a potential false positive error
Previous by thread: Bug#1005326: no-code-sections triggered on non-ELF files
Next by thread: Bug#1005326: no-code-sections triggered on non-ELF files
Index(es):
- Date
- Thread