From: Christopher Faylor <me@cgf.cx>
To: Mark Mitchell <mark@codesourcery.com>,
paul@codesourcery.com, gdb@sourceware.org
Subject: Re: Windows support in GDB
Date: Fri, 29 Apr 2005 16:36:00 -0000 [thread overview]
Message-ID: <20050429162732.GA12864@trixie.casa.cgf.cx> (raw)
In-Reply-To: <42725D6A.7040103@codesourcery.com>
On Fri, Apr 29, 2005 at 09:14:34AM -0700, Mark Mitchell wrote:
>Christopher Faylor wrote:
>>While I am the Windows maintainer for gdb, I have been thinking that
>>maybe I might have to step down if it means that I'll have to support a
>>Windows configuration for which I have little interest.
>
>I think that would be a shame.
>
>>I haven't asked what the problem is with just using cygwin with gdb. I
>>suspect that the standard two problems are:
>
>You might ask the MinGW community why they exist. :-)
I'm a member of the MinGW community and admirer of MinGW but,
unfortunately, that doesn't necessarily translate into my wanting to
support gdb-on-windows-sans-cygwin.
So far, I've had no problems with the patches being applied. I've
been asking people in the MinGW community to submit patches for
a long time.
However, now that the patches are finally here, I have to say that I
sort of share Mark K's concerns. I'm wondering if we are on a slippery
slope and (to mix a metaphor) will be subjecting gdb to a
death-by-inches as we slowly add ifdefs throughout the configury and
code.
>One reason to use MinGW is that you're using other tools that rely on
>Windows paths, and don't understand Cygwin mount points. Or you
>yourself don't understand Cygwin mount points. :-)
You don't have to use windows mount points if you don't want to. AFAIK,
normal windows paths have been working in gdb for a while. I'm not talking
about requiring a complete cygwin environment to run gdb. In theory,
all that you really need is "gdb.exe + cygwin1.dll".
But, as you said, this discussion probably isn't worthwhile. Customers
want what they want.
cgf
next prev parent reply other threads:[~2005-04-29 16:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 15:32 Mark Kettenis
2005-04-29 15:32 ` Daniel Jacobowitz
2005-04-29 16:08 ` Christopher Faylor
2005-04-29 16:31 ` Mark Mitchell
2005-04-29 16:36 ` Christopher Faylor [this message]
2005-04-29 16:47 ` Mark Mitchell
2005-04-29 16:56 ` Christopher Faylor
2005-04-29 17:05 ` Mark Mitchell
2005-04-29 17:16 ` Christopher Faylor
2005-05-01 20:13 ` Eli Zaretskii
2005-05-01 19:50 ` Eli Zaretskii
2005-04-29 16:52 ` Dave Korn
2005-04-29 16:57 ` Mark Mitchell
2005-04-29 17:00 ` Dave Korn
2005-04-30 16:18 ` Mark Kettenis
2005-04-30 20:37 ` Christopher Faylor
2005-05-01 20:05 ` Eli Zaretskii
2005-05-01 20:06 ` Mark Mitchell
2005-05-01 20:24 ` Eli Zaretskii
2005-04-29 16:32 ` Kris Warkentin
2005-04-29 16:40 ` Christopher Faylor
2005-04-29 17:00 ` Kris Warkentin
2005-05-01 19:55 ` Eli Zaretskii
2005-05-01 21:41 ` Christopher Faylor
2005-05-02 19:03 ` Eli Zaretskii
2005-05-02 19:56 ` Christopher Faylor
2005-04-29 16:48 ` Daniel Jacobowitz
2005-04-29 17:33 ` Christopher Faylor
2005-04-29 17:58 ` Daniel Jacobowitz
2005-04-29 19:08 ` Christopher Faylor
2005-04-29 19:36 ` Daniel Jacobowitz
2005-04-29 22:01 ` Christopher Faylor
2005-05-02 15:41 ` Andrew Cagney
2005-05-02 15:45 ` Daniel Jacobowitz
2005-04-29 16:04 ` Kris Warkentin
2005-04-29 16:23 ` Mark Mitchell
2005-04-29 16:46 ` Christopher Faylor
2005-04-29 16:50 ` Mark Mitchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050429162732.GA12864@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gdb@sourceware.org \
--cc=mark@codesourcery.com \
--cc=paul@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox