From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3746 invoked by alias); 16 Apr 2009 07:09:09 -0000 Received: (qmail 3723 invoked by uid 22791); 16 Apr 2009 07:09:06 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Apr 2009 07:09:01 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 8B5562BAC35; Thu, 16 Apr 2009 03:08:59 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kAYgB2QzhkPj; Thu, 16 Apr 2009 03:08:59 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 58D332BAC09; Thu, 16 Apr 2009 03:08:59 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id B90F5F5BA6; Thu, 16 Apr 2009 00:08:55 -0700 (PDT) Date: Thu, 16 Apr 2009 09:00:00 -0000 From: Joel Brobecker To: Lennyk Cc: gdb@sourceware.org Subject: Re: Core dump information when code is optimized Message-ID: <20090416070855.GI7603@adacore.com> References: <49E6D676.9000108@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49E6D676.9000108@gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00135.txt.bz2 > Is there a way to get this information with core dump - but maintain the > optimized sized executable? The -O flags are completely independent from debugging information. In order to do symbolic debugging, GDB needs debugging information, which is why using the -g switch helps. There might be a way to produce only line number information if that's what you need, but I don't know offhand. Check the compiler/linker docs. Regardless, the extra info will cause the size of your executable to grow, as you have discovered. -- Joel