From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-418776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23712 invoked by alias); 29 Mar 2013 20:56:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 23674 invoked by uid 48); 29 Mar 2013 20:56:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/56783] g++ does not supply signatures for gdb on g++ 4.7 versions
Date: Fri, 29 Mar 2013 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-56783-4-uMRBS4d9zl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56783-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
X-SW-Source: 2013-03/txt/msg02217.txt.bz2


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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-03-29 20:56:29 UTC ---
(In reply to comment #4)
> 
> Johanathan, 4.2 was NOT a typo.  That was the version of g++ that came with
> Snow Leopard.  It was failing.  I replaced it by version 4.7 obtained from
> SourceForge, and it fails in EXACTLY the same way.

Then the problem is unlikely to be GCC.  I'm fairly sure Apple's modified GCC
4.2 should work with their own OS and linker.  Maybe the problem is with your
GDB version, which you haven't stated.

> Therefore, the linker must be adding the "signatures" to the linked module,
> probably by reading the object decks AND the source files.  But that only seems
> to be happening with g++ 4.0.1 and associated linker.  The linker with versions
> 4.2 and higher must have revised linkers that DO NOT create the "signatures".

GCC doesn't have an associated linker, it is using the Apple linker that comes
with the OS.