From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3483 invoked by alias); 2 Oct 2004 09:03:35 -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 3468 invoked from network); 2 Oct 2004 09:03:31 -0000 Received: from unknown (HELO outbound0.sv.meer.net) (205.217.152.13) by sourceware.org with SMTP; 2 Oct 2004 09:03:31 -0000 Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id i92932r2036195 for ; Sat, 2 Oct 2004 02:03:02 -0700 (PDT) (envelope-from dmose@meer.net) Received: from [192.168.1.102] (dsl081-050-187.sfo1.dsl.speakeasy.net [64.81.50.187]) by mail.meer.net (8.12.10/8.12.2/meer) with ESMTP id i9292xT2009146 for ; Sat, 2 Oct 2004 02:02:59 -0700 (PDT) (envelope-from dmose@meer.net) Message-ID: <415E6EA9.5080701@meer.net> Date: Sat, 02 Oct 2004 15:14:00 -0000 From: Dan Mosedale User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: gdb@sourceware.org Subject: Re: Building GDB with MinGW (3) References: <20041001151052.70124.qmail@web11904.mail.yahoo.com> <20041001151613.12427.qmail@web11903.mail.yahoo.com> <20041001165127.GI26324@gnat.com> <415E1045.7030109@meer.net> <20041002033743.GE14081@trixie.casa.cgf.cx> In-Reply-To: <20041002033743.GE14081@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00016.txt.bz2 Christopher Faylor wrote: > Joel Brobecker wrote: > >>>>real problem. (READLINE) >>>> >>>> >>>As far as I can remember, GDB has not been ported to MingW. And indeed, porting readline is one of the problems to solve for that port. There is a group that has posted patches that allow you to build GDB on MingW, they have a web site. I don't know the URL but google should help you find it. Last I heard, they had ported GDB 5.3, but maybe they have patches for a more recent release now. >>> >>> >>Actually, it has. See . >> >> > >Maybe at some point someone will actually do it right and try to submit >patches to gdb. > > On the up side, the author says in his patch, "These changes have yet to be submitted for review." This would seem to imply that he intends for them to land back in the mainline in the future. >>One of the tarballs for the most recent snapshot version includes the >>patch against the mainline. It's from around May, so I suspect the >>patch will require some massaging if you want it to work against >>current CVS. The best thing about the port is that, unlike the cygwin >>port, hitting ^c to stop the inferior seems to actually work most of >>the time (assuming you run the gdb in a cmd window and not a cygwin >>window). This is because it relies on windows native events rather >>than cygwin signals. >> >> > >CTRL-C works fine on cygwin. I use it all of the time. > >In fact, CTRL-C does not rely on cygwin signals. gdb doesn't know about >cygwin signals from the inferior process. I haven't looked at what >mingw does but it is likely to be the same code. > > You're right on all counts; sorry for the misinformation. I looked into this once many moons ago, and completely misremembered the details. Dan