From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4328 invoked by alias); 22 Dec 2007 22:49:33 -0000 Received: (qmail 4319 invoked by uid 22791); 22 Dec 2007 22:49:32 -0000 X-Spam-Check-By: sourceware.org Received: from mail.suse.de (HELO mx1.suse.de) (195.135.220.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 22 Dec 2007 22:49:26 +0000 Received: from Relay1.suse.de (relay-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.suse.de (Postfix) with ESMTP id A9DD424E8A; Sat, 22 Dec 2007 23:49:23 +0100 (CET) To: Ian Lance Taylor Cc: gcc@gcc.gnu.org Subject: Re: Designs for better debug info in GCC From: Andi Kleen References: <7C283DB3-9716-4B2C-9721-D1F503B91CC4@apple.com.suse.lists.egcs> Date: Sun, 23 Dec 2007 00:52:00 -0000 In-Reply-To: (Ian Lance Taylor's message of "Sat\, 22 Dec 2007 18\:15\:04 +0000 \(UTC\)") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg00665.txt.bz2 Ian Lance Taylor writes: > I'm in favor of implementing this. Yes it would be great. > As I'm sure you know, the GNU > binutils Actually binutils only barely supports debuginfo. AFAIK objcopy is the tool tool that knows anything about them. > and gdb already support using a single separate file for > debugging information. That does not solve that problem because all that data still has to be copied. In the current setup even two times (.o -> exe -> objcopy to debuginfo and then another strip which is another partial write). I assume that copying phase is the problem people are complaining about and debuginfo makes it even worse now. > well during development for a program which is normally run on the > same system on which it is developed. It doesn't help much when the > program must be run on a different system--it's possible to use > gdbserver, but awkward. And it doesn't help at all when it is > sometimes necessary to debug executables which have been built and > distributed widely. The Linux distributions have debuginfo rpms that work fine for that. But it does not solve the link time IO problem. -Andi