Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 19:08:00 -0000	[thread overview]
Message-ID: <20050429185956.GB17283@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20050429175745.GA753@nevyn.them.org>

On Fri, Apr 29, 2005 at 01:57:45PM -0400, Daniel Jacobowitz wrote:
>On Fri, Apr 29, 2005 at 01:16:31PM -0400, Christopher Faylor wrote:
>>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.
>
>OK, I see your point.  I think we're talking past each other, though -
>this comes back to Kris's point about consistency.  Shipping a mingw
>GCC and a cygwin GDB is error-prone, especially if we otherwise do not
>need the cygwin DLL.

I don't see why this is an issue.  It would take a little bit of work to
make sure you didn't stomp on an existing cygwin installation but
putting a cygwin1.dll in the same directory as gdb.exe is a pretty
time-tested way of releasing packages on Windows.  Many packages release
executables + dlls.

Cygwin is problematic because it is constantly evolving and adding new
features and, so, there will be issues if you try to use an old DLL with
a newer binary but, again, this is not an insurmountable problem.

cgf


  reply	other threads:[~2005-04-29 19:01 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
2005-04-29 17:58         ` Daniel Jacobowitz
2005-04-29 19:08           ` Christopher Faylor [this message]
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=20050429185956.GB17283@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