X-Spam-Check-By:	sourceware.org
Message-ID:	<43975199.5E8BE731@dessent.net>
Date:	Wed, 07 Dec 2005 13:18:17 -0800
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Extracting Debug (meta data) from executable images?
References:	<23239280 DOT 1133989199317 DOT JavaMail DOT SYSTEM AT CCC-NOVA1>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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.

Brian

--
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/

- Raw text -