public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/60465] Compiling glibc-2.17,2.18 with gcc-4.8.2 and binutils-2.23.2,2.24 results in segfaults in _start / elf_get_dynamic_info
Date: Wed, 19 Mar 2014 05:35:00 -0000	[thread overview]
Message-ID: <bug-60465-4-gzb62bj0a1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60465-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60465

--- Comment #5 from Mike Frysinger <vapier at gentoo dot org> ---
Created attachment 32385
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32385&action=edit
gdb session

here's the trace from the first insn where dyn is pointing to DT_GNU_HASH.  at
this point, it has processed DT_SONAME and DT_HASH.

$ readelf -d build/elf/ld.so

Dynamic section at offset 0x3c8b8 contains 20 entries:
  Tag        Type                         Name/Value
 0x000000000000000e (SONAME)             Library soname: [ld-linux-ia64.so.2]
 0x0000000000000004 (HASH)               0x190
 0x000000006ffffef5 (GNU_HASH)           0x2d8
 0x0000000000000005 (STRTAB)             0x998


  parent reply	other threads:[~2014-03-19  5:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08 12:08 [Bug other/60465] New: " devurandom at gmx dot net
2014-03-08 12:09 ` [Bug other/60465] " devurandom at gmx dot net
2014-03-18  7:18 ` vapier at gentoo dot org
2014-03-18  7:29 ` devurandom at gmx dot net
2014-03-18 10:31 ` schwab@linux-m68k.org
2014-03-19  5:35 ` vapier at gentoo dot org [this message]
2014-03-25 18:23 ` devurandom at gmx dot net
2014-03-25 22:17 ` vapier at gentoo dot org
2014-03-25 23:01 ` devurandom at gmx dot net
2014-08-14  3:26 ` vapier at gentoo dot org
2014-08-14  7:13 ` ebotcazou at gcc dot gnu.org
2014-08-14  7:21 ` ebotcazou at gcc dot gnu.org
2014-08-14  7:35 ` pinskia at gcc dot gnu.org
2014-08-14 11:55 ` vapier at gentoo dot org
2014-08-14 11:57 ` vapier at gentoo dot org
2014-08-14 12:27 ` vapier at gentoo dot org
2014-08-16 14:22 ` vapier at gentoo dot org
2014-08-16 14:27 ` vapier at gentoo dot org
2014-08-16 14:28 ` vapier at gentoo dot org
2014-08-16 15:40 ` ebotcazou at gcc dot gnu.org
2014-08-18  7:58 ` rguenth at gcc dot gnu.org
2014-08-18 14:08 ` ebotcazou at gcc dot gnu.org
2014-08-18 21:14 ` ebotcazou at gcc dot gnu.org
2014-08-19  0:16 ` vapier at gentoo dot org
2014-08-19 21:46 ` ebotcazou at gcc dot gnu.org
2014-08-19 22:02 ` ebotcazou at gcc dot gnu.org

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-60465-4-gzb62bj0a1@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).