From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24777 invoked by alias); 13 Feb 2004 03:03:13 -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 24723 invoked from network); 13 Feb 2004 03:03:11 -0000 Received: from unknown (HELO yosemite.airs.com) (209.128.65.135) by sources.redhat.com with SMTP; 13 Feb 2004 03:03:11 -0000 Received: (qmail 13019 invoked by uid 10); 13 Feb 2004 03:03:10 -0000 Received: (qmail 32198 invoked by uid 500); 13 Feb 2004 03:03:02 -0000 From: Ian Lance Taylor To: Bob Rossi Cc: gdb@sources.redhat.com Subject: Re: Executable's debug format References: <20040213005432.GA4476@white> Date: Fri, 13 Feb 2004 03:03:00 -0000 In-Reply-To: <20040213005432.GA4476@white> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-02/txt/msg00130.txt.bz2 Bob Rossi writes: > Is there a way to find out what debug format the debugging info in the > executable is in? Yes, but I don't know of a trivial way. Run objdump -h to see the sections. If the program has a .debug it is using DWARF 1. If the program has a .debug_info it is using DWARF 2. If the program has .stab and .stabstr sections it is using stabs debugging information. There are many other possibilities, though those are the most common these days. > Or is it more complicated? Can a single executable be composed of object > files which each have there debugging info in a different format? Yes, that is possible, though very unusual. Ian