This is the mail archive of the
mailing list for the GDB project.
Re: Windows support in GDB
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Kris Warkentin <kewarken at qnx dot com>
- Cc: me at cgf dot cx, mark at codesourcery dot com, paul at codesourcery dot com, gdb at sourceware dot org
- Date: Sun, 01 May 2005 22:51:02 +0300
- Subject: Re: Windows support in GDB
- References: <200504291513.j3TFDhjx021040@elgar.sibelius.xs4all.nl> <20050429153146.GA27362@nevyn.them.org> <20050429160040.GH10017@trixie.casa.cgf.cx> <firstname.lastname@example.org> <20050429163011.GB12864@trixie.casa.cgf.cx> <427267B7.email@example.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 29 Apr 2005 12:58:31 -0400
> From: Kris Warkentin <firstname.lastname@example.org>
> CC: email@example.com, firstname.lastname@example.org, email@example.com
> It isn't just an issue of gdb not working with native paths because,
> as you say, it _usually_ does. It's a question of consistency.
In fact, any serious use of GDB will almost instantly bump into such a
consistency (or lack thereof) issue. For example, will the `edit' and
`shell' commands work if I don't have a Cygwin Bash installed and GDB
is configured to invoke that Bash as the shell?