public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/5929] New: VALID_ELF_HEADER is not used for the executable
Date: Thu, 13 Mar 2008 12:37:00 -0000	[thread overview]
Message-ID: <20080313123637.5929.drow@sources.redhat.com> (raw)

I'm working on a project that involves bumping the EI_ABIVERSION, since new
binaries require loader support.  We wanted a sensible error message when using
an old loader, but it doesn't work unless you run ld.so by hand:

$ /lib/ld.so.1 ./newtest.exe
./newtest.exe: error while loading shared libraries: ./newtest.exe: ELF file ABI
version invalid
$ ./newtest.exe
Segmentation fault (core dumped)

VALID_ELF_HEADER is only used when loading a new file; it is never applied to
the mapped executable when ld.so is the interpreter.

-- 
           Summary: VALID_ELF_HEADER is not used for the executable
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: drow at sources dot redhat dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5929

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2008-03-13 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 12:37 drow at sources dot redhat dot com [this message]
2008-03-13 14:35 ` [Bug libc/5929] " drepper at redhat dot com
2008-03-13 14:44 ` drow at sources dot redhat 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=20080313123637.5929.drow@sources.redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).