Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning:	makita.cygnus.com: keiths owned process doing -bs
Date:	Tue, 20 Nov 2001 06:00:47 -0800 (PST)
From:	Keith Seitz <keiths AT cygnus DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: gdb trouble
In-Reply-To:	<3BFA5F92.5000807@cportcorp.com>
Message-ID:	<Pine.GSO.4.33.0111200553460.19213-100000@makita.cygnus.com>
MIME-Version:	1.0

On Tue, 20 Nov 2001, Peter Buckley wrote:

> I presuppose that it doesn't understand /cygdrive and mount points, so
> it doesn't compute /usr/bin to mean c:\cygwin\bin.

Probably not a bad guess, but allow me to enumerate what Insight can and
cannot do (for the record). At least as far as I know:

When using the file menu's Open option, users open an exe for debugging by
using the Window's file selection dialog, which knows nothing about
cygwin (of course).

When using the console window to specify filenames, it is (or should be)
100% aware that /bin is c:/cygwin/bin, just as gdb does (or should).

I'm not sure where else command-line gdb and Insight differ w.r.t.
filenames (which is why I asked my original question).

Of course, I could be missing something obvious.
Keith


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -