public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jmbnyc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29244]  New: bad relocation section name
Date: Tue, 26 Sep 2006 20:44:00 -0000	[thread overview]
Message-ID: <bug-29244-13105@http.gcc.gnu.org/bugzilla/> (raw)

I continue to get the errors below when trying to link fairly straight forward
C++ programs. The same code will compile/link fine with the opposite compile
type (the two compile types are -O2 and -g). If I mod the code slighly, I can
usually narrow it down to a single line that when commented out allows the link
to occur. Can anyone tell me what the origin of this message is and why it
might be generated from the linker.
/JMB

collect2: ld terminated with signal 11 [Segmentation fault]
/usr/bin/ld: build/ia32.linux/gcc32/cc-g/subscribeClient.o: bad
relocation section name `'

collect2: ld terminated with signal 11 [Segmentation fault]
/usr/bin/ld: build/ia32.linux/gcc32/cc-O2/publishClient.o: bad
relocation section name `'


-- 
           Summary: bad relocation section name
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jmbnyc at gmail dot com
 GCC build triplet: gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
  GCC host triplet: linux fc5 2.6.17-1.2187_FC5
GCC target triplet: x86-64 and ia32


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


             reply	other threads:[~2006-09-26 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 20:44 jmbnyc at gmail dot com [this message]
2006-09-26 20:46 ` [Bug c++/29244] " pinskia at gcc dot gnu dot org
2006-09-26 20:58 ` jmbnyc at gmail dot com
2006-10-05 18:19 ` pinskia at gcc dot gnu dot 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-29244-13105@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).