public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/29244]  New: bad relocation section name
@ 2006-09-26 20:44 jmbnyc at gmail dot com
  2006-09-26 20:46 ` [Bug c++/29244] " pinskia at gcc dot gnu dot org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: jmbnyc at gmail dot com @ 2006-09-26 20:44 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/29244] bad relocation section name
  2006-09-26 20:44 [Bug c++/29244] New: bad relocation section name jmbnyc at gmail dot com
@ 2006-09-26 20:46 ` 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
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-09-26 20:46 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2006-09-26 20:46 -------
collect2: ld terminated with signal 11 [Segmentation fault]
/usr/bin/ld: build/ia32.linux/gcc32/cc-g/subscribeClient.o: bad
relocation section name `'

This is most likely a bug in your binutils you have install.
I would first suggest you to update your FC5 and if that does not work, then
report this to Redhat.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/29244] bad relocation section name
  2006-09-26 20:44 [Bug c++/29244] New: bad relocation section name jmbnyc at gmail dot com
  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
  2 siblings, 0 replies; 4+ messages in thread
From: jmbnyc at gmail dot com @ 2006-09-26 20:58 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from jmbnyc at gmail dot com  2006-09-26 20:58 -------
Subject: Re:  bad relocation section name

As I suggested in my post, I am fully updated as of one hour ago. I
reported the problem to redhat last week and never received a
response. Do you have any idea what 'bad relocation section name'
means and why it might appear?
/JMB

On 26 Sep 2006 20:46:48 -0000, pinskia at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #1 from pinskia at gcc dot gnu dot org  2006-09-26 20:46 -------
> collect2: ld terminated with signal 11 [Segmentation fault]
> /usr/bin/ld: build/ia32.linux/gcc32/cc-g/subscribeClient.o: bad
> relocation section name `'
>
> This is most likely a bug in your binutils you have install.
> I would first suggest you to update your FC5 and if that does not work, then
> report this to Redhat.
>
>
> --
>
> pinskia at gcc dot gnu dot org changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |INVALID
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29244
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>


-- 


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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug c++/29244] bad relocation section name
  2006-09-26 20:44 [Bug c++/29244] New: bad relocation section name jmbnyc at gmail dot com
  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
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-10-05 18:19 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from pinskia at gcc dot gnu dot org  2006-10-05 18:18 -------
*** Bug 29359 has been marked as a duplicate of this bug. ***


-- 


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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-10-05 18:19 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-09-26 20:44 [Bug c++/29244] New: bad relocation section name jmbnyc at gmail dot com
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

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).