public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/11615] New: ld.so segfaults when RLD_MAP is 0 Date: Thu, 20 May 2010 12:51:00 -0000 [thread overview] Message-ID: <20100520125121.11615.aurelien@aurel32.net> (raw) Broken ELF binaries that have RLD_MAP equals to 0 (it seems to be possible to generate them linking it with --version-script) are causing a segfault of ld.so, even in --list or --verify mode. While this is obviously a bug in the ELF binary, ld.so should not segfault in this case. -- Summary: ld.so segfaults when RLD_MAP is 0 Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: ports AssignedTo: roland at gnu dot org ReportedBy: aurelien at aurel32 dot net CC: glibc-bugs at sources dot redhat dot com GCC build triplet: mipsel-unknown-linux-gnu GCC host triplet: mipsel-unknown-linux-gnu GCC target triplet: mipsel-unknown-linux-gnu http://sourceware.org/bugzilla/show_bug.cgi?id=11615 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-05-20 12:51 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-20 12:51 aurelien at aurel32 dot net [this message] 2010-05-20 12:52 ` [Bug ports/11615] " aurelien at aurel32 dot net
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=20100520125121.11615.aurelien@aurel32.net \ --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: linkBe 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).