X-Spam-Check-By: sourceware.org Date: Wed, 7 Dec 2005 16:27:00 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Extracting Debug (meta data) from executable images? Message-ID: <20051207212700.GC30968@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <23239280.1133989199317.JavaMail.SYSTEM@CCC-NOVA1> <43975199.5E8BE731@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43975199.5E8BE731@dessent.net> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Dec 07, 2005 at 01:18:17PM -0800, Brian Dessent wrote: >Siegfried Heintze wrote: >>What is the relationship between cygwin, windows and these formats and >>libraries? Can I use these linux libraries to read debug information >>in images created with g++ on cygwin? >> >>If not, how do I read the debug information in images created with g++ >>on cygwin? > >The gcc / binutils / gdb distributed with Cygwin use stabs. I believe >that patches to get dwarf2 working have been submitted, and in theory >if you build your own toolchain you should be able to do this. > >But "extracting debug info" is way too vague of a term to offer any >meaningful help. You'd have to state exactly what you're trying to do. >Try "man objdump" or "objdump -g file", or read the binutils/bfd >internals manuals. But despite all of this, I'm sure Igor is still pleased... cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/