From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19506 invoked by alias); 2 Dec 2010 09:10:05 -0000 Received: (qmail 19494 invoked by uid 22791); 2 Dec 2010 09:10:04 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_GD X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 02 Dec 2010 09:10:00 +0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/46749] gcc.dg/debug/pr41893-1.c -gdwarf-2 testsuite failures on darwin 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: iains at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 02 Dec 2010 09:10:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-12/txt/msg00152.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46749 --- Comment #20 from Iain Sandoe 2010-12-02 09:09:49 UTC --- (In reply to comment #19) > On Wed, 1 Dec 2010, iains at gcc dot gnu.org wrote: > > yeah - it's on my TODO (pr43751). > > FWIW, some time ago, I did enquire about the difficulty of adding an > > intentional additional post-link phase, with the feedback that it was prob. not > > easy. > > I thought about adding it to the collect-ld script instead. > > Why do we want it only if there is a .c source available? That doesn't > make sense to me ... but i have no idea what dsymutil is supoosed to do, > so ... _any_ source, in fact -- hence PR43751 (because we don't even try to notice Fortran at present). ---- OK. Without wishing to start any debate on whether the approach is "good" or "bad". The idea is that one saves time in the compile/debug loop by _not_ linking the debug - and leaving it in the object files. This is fine until the c/l is of the form " gcc some-source.ext -o exe " because then the object is temporary and deleted, thus not available for debugging. So, dsymtuil (which is a stand-alone debug-linker - used, in general, for the packaging phase of a project) is invoked for such command lines. It grabs the debug from the files that will be deleted during the build. this is quite helpful: http://wiki.dwarfstd.org/index.php?title=Apple's_%22Lazy%22_DWARF_Scheme