public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jpalus at fastmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28990] New: ld.so --verify segfaults on cc1 binary on arm 32bit
Date: Tue, 22 Mar 2022 15:27:34 +0000	[thread overview]
Message-ID: <bug-28990-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28990
           Summary: ld.so --verify segfaults on cc1 binary on arm 32bit
           Product: glibc
           Version: 2.35
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: jpalus at fastmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Created attachment 14032
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14032&action=edit
ld.so/cc1

ld.so --verify cc1 segfaults with attached files on arm 32bit (these are
arm6hf, but verified behavior is the same also on armv7hf).

For plenty other binaries it works fine, it appears to have issues with those
coming from gcc though.

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

             reply	other threads:[~2022-03-22 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 15:27 jpalus at fastmail dot com [this message]
2022-03-22 15:53 ` [Bug libc/28990] " jpalus at fastmail dot com
2022-03-23 19:10 ` jpalus at fastmail dot com
2022-03-23 23:46 ` jpalus at fastmail dot com
2022-03-24  9:04 ` schwab@linux-m68k.org
2022-03-30 12:50 ` jpalus at fastmail dot com

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-28990-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).