X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Eric Lilja <mindcooler AT gmail DOT com>
Subject:	Debugging question
Date:	Tue, 12 Feb 2008 00:45:41 +0100
Lines:	20
Message-ID:	<foqmn4$nio$1@ger.gmane.org>
Mime-Version:	1.0
User-Agent:	Thunderbird 2.0.0.9 (Windows/20071031)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

I have a native windows program (compiled using cygwin's gcc acting in 
mingw mode, with debugging information), can I debug it using cygwin's 
gdb? It's emacs I'm talking about and I'm trying to provide the 
developers information about a crash on windows vista. Doing this works 
fine:
$ gdb emacs
$ run -Q
crash!
$ bt
I see function names, files and line numbers involved before the crash. 
Now I want to put a breakpoint somewhere and print some variables when 
that breakpoint is hit. Can I do that in this scenario? If so, how do I 
make gdb find emacs sources? Doing
$ break /cygdrive/c/full/path/to/source/file:1337 doesn't work (No 
source file named blah blah).
If these questions, which basically is about gdb usage and mixing mingw 
compiled binaries with cygwin tools is considered off-topic, I sincerly 
apologise.

- Eric Lilja


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