From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3562 invoked by alias); 8 Sep 2004 00:33:49 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3547 invoked from network); 8 Sep 2004 00:33:47 -0000 Received: from unknown (HELO universe.preston.net) (202.14.89.130) by sourceware.org with SMTP; 8 Sep 2004 00:33:47 -0000 Received: from cosmo.preston.net (cosmo.preston.net [202.14.10.54]) by universe.preston.net (8.11.6/8.11.6) with ESMTP id i880Xiq27399 for ; Wed, 8 Sep 2004 10:33:45 +1000 Subject: gdb acceptance of gcc's -feliminate-dwarf2-dups code From: Craig Jeffree To: gdb@sources.redhat.com Content-Type: text/plain Organization: Preston Aviation Solutions Message-Id: <1094603624.14297.88.camel@cosmo.preston.net> Mime-Version: 1.0 Date: Wed, 08 Sep 2004 00:33:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00060.txt.bz2 Hi, Back in January someone provided a patch to allow gdb to accept code generated with the gcc option -feliminate-dwarf2-dups. This patch could not be accepted for various reasons detailed in a thread on gdb-patches (http://sources.redhat.com/ml/gdb-patches/2004-01/msg00386.html). At the time others indicated that this feature would be added very soon, however it appears as though it is still outstanding. Is this correct? Is anyone working on a patch for this feature? We are stuck using gcc 2.95.3 because our debug binary is over 900M already, it gets _much_ bigger if we use gcc 3.x - however this duplicate removal helps keep the blowout somewhat reasonable. Are there others who need this patch? Cheers, Craig.