From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12572 invoked by alias); 29 Apr 2005 19:08:04 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12286 invoked from network); 29 Apr 2005 19:07:56 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 29 Apr 2005 19:07:56 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DRaqB-00016Z-P2; Fri, 29 Apr 2005 15:07:55 -0400 Date: Fri, 29 Apr 2005 19:36:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Cc: mark@codesourcery.com, paul@codesourcery.com Subject: Re: Windows support in GDB Message-ID: <20050429190755.GA4174@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org, mark@codesourcery.com, paul@codesourcery.com References: <200504291513.j3TFDhjx021040@elgar.sibelius.xs4all.nl> <20050429153146.GA27362@nevyn.them.org> <20050429160040.GH10017@trixie.casa.cgf.cx> <20050429164508.GA30548@nevyn.them.org> <20050429171631.GH12864@trixie.casa.cgf.cx> <20050429175745.GA753@nevyn.them.org> <20050429185956.GB17283@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050429185956.GB17283@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-04/txt/msg00241.txt.bz2 On Fri, Apr 29, 2005 at 02:59:56PM -0400, Christopher Faylor wrote: > 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. I'm afraid I don't know any more about it than I've already said. I don't have a lot of experience with Cygwin. One problem I seem to recall is that you can't put the new binary in your $PATH and use it from Cygwin without removing the second copy of the DLL. -- Daniel Jacobowitz CodeSourcery, LLC