public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28749] Inconsistency detected by ld.so: rtld.c: 1632: dl_main: Assertion `GL(dl_rtld_map).l_libname' failed!
Date: Fri, 07 Jan 2022 13:48:22 +0000	[thread overview]
Message-ID: <bug-28749-131-BFHpYLdm2e@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28749-131@http.sourceware.org/bugzilla/>

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.35
             Status|ASSIGNED                    |RESOLVED

--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
Fixed via:

commit 6b0978c14acc2a6b5f5dbd8e8ef75fddc6656483
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Jan 7 14:47:31 2022 +0100

    Restore ENTRY_POINT definition on hppa, ia64 (bug 28749)

    ENTRY_POINT is still needed for elf/rtld.c.  Fixes commit 4fb4e7e821e3
    ("csu: Always use __executable_start in gmon-start.c").

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

      parent reply	other threads:[~2022-01-07 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 22:36 [Bug libc/28749] New: " danglin at gcc dot gnu.org
2022-01-07  8:58 ` [Bug libc/28749] " fweimer at redhat dot com
2022-01-07  9:02 ` fweimer at redhat dot com
2022-01-07 13:48 ` fweimer at redhat dot com [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-28749-131-BFHpYLdm2e@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).