From: Jurij Smakov <jurij@wooyd.org>
To: sparclinux@vger.kernel.org
Subject: Re: mmap breakage
Date: Tue, 07 Dec 2004 15:38:02 +0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0412071028590.2693@bobcat> (raw)
In-Reply-To: <Pine.LNX.4.61.0412032354010.1963@bobcat>
On Mon, 6 Dec 2004, David S. Miller wrote:
> What needs to execute ld-linux.so.2 directly in order to run
> and has a huge data section? :-) Is it some part of the GLIBC
> build, perhaps during locale generation?
No, this bug has been triggered during autobuilding of at least two
different Debian packages, kmd [0] and fet [1]. kmd is a graphical
debugger for ARM boards, and fet is some sort of personal organizer.
When ldd is run on the binaries late in the building stage to extract
the information about the dynamic libraries and generate the correct
dependencies, it (among other things) invokes the command:
/lib/ld-linux.so.2 --verify ./a.out
which fails with SIGILL, if one is unlucky.
[0] http://bugs.debian.org/268450
[1] http://buildd.debian.org/fetch.php?&pkgþt&ver=3.9.19-1&arch=sparc&stamp\x1101448389&file=log&as=raw
Best regards,
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
next prev parent reply other threads:[~2004-12-07 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 5:22 mmap breakage Jurij Smakov
2004-12-04 23:13 ` Richard Mortimer
2004-12-04 23:16 ` Richard Mortimer
2004-12-06 4:30 ` Jurij Smakov
2004-12-06 5:23 ` David S. Miller
2004-12-07 6:00 ` Jurij Smakov
2004-12-07 6:06 ` David S. Miller
2004-12-07 6:11 ` Keith M Wesolowski
2004-12-07 6:20 ` David S. Miller
2004-12-07 6:31 ` Jurij Smakov
2004-12-07 7:47 ` David S. Miller
2004-12-07 8:24 ` Jakub Jelinek
2004-12-07 15:38 ` Jurij Smakov [this message]
2004-12-08 0:54 ` Richard Mortimer
2004-12-09 5:24 ` David S. Miller
2004-12-09 7:34 ` David S. Miller
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=Pine.LNX.4.61.0412071028590.2693@bobcat \
--to=jurij@wooyd.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.