From: Christopher Faylor <me@cgf.cx>
To: mark@codesourcery.com, paul@codesourcery.com, gdb@sourceware.org
Subject: Re: Windows support in GDB
Date: Fri, 29 Apr 2005 17:33:00 -0000 [thread overview]
Message-ID: <20050429171631.GH12864@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20050429164508.GA30548@nevyn.them.org>
On Fri, Apr 29, 2005 at 12:45:08PM -0400, Daniel Jacobowitz wrote:
>On Fri, Apr 29, 2005 at 12:00:40PM -0400, Christopher Faylor wrote:
>> Of course it does build "out of the box" on Windows right now if you
>> have cygwin.
>
>Sorry, very bad choice of wording on my part.
>
>> 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.
>
>That would definitely suck! If you are uninterested in MinGW support
>(perfectly reasonable) then I'd prefer that you clarify your
>maintenance to just cover Cygwin. You do a great job for Cygwin, and
>the big reason we've been bugging you about Windows patches is that you
>seem to know more about it than we do :-)
Hopefully, I do know a lot about Windows programming (unfortunately).
Maintaining cygwin means knowing a lot about Windows and UNIX.
I guess the thought of coming up with a solution in cygwin that has to
be dealt with in a different fashion in gdb/mingw is a little daunting.
However, I'm not going anywhere. I'm calmed down now. :-)
>> I haven't asked what the problem is with just using cygwin with gdb.
>> I suspect that the standard two problems are:
>>
>> 1) cygwin is "slow" (which really only is an issue for configure/make)
>
>Our customers have found, I think, that this is true for more than just
>shell/fork-heavy loads; it was also true for GCC. Treat this as
>hearsay, though. I've never measured it myself.
It seems like my point wasn't clear here. I know that cygwin is slow.
I'm talking about just using gdb for debugging. If your customers are
routinely rebuilding gdb, then the slowness would be an issue. If they
are not, then unless cygwin was adding some kind of 10x slowdown to
debugging, I don't see why it would be an issue.
>> 2) You can't trivially include your own version of cygwin1.dll with
>> a distribution since it could conflict with a version already on
>> the system.
>>
>> I can't do much to address 1 but 2 is not an insurmountable problem.
>
>Sure. But I somewhat approve of mingw-only installations because of
>the number of times I've installed a vendor's carelessly packaged
>cygwin tools and had them trash my existing Cygwin installation. I do
>use Cygwin, so that ticks me off :-) It's not an insurmountable
>problem but people seem to have a great deal of trouble surmounting it.
No argument there. It is a continual source of frustration.
cgf
next prev parent reply other threads:[~2005-04-29 17:16 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
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 [this message]
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=20050429171631.GH12864@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