From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29718 invoked by alias); 16 Jun 2011 13:54:29 -0000 Received: (qmail 29710 invoked by uid 22791); 16 Jun 2011 13:54:28 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from ausc60ps301.us.dell.com (HELO ausc60ps301.us.dell.com) (143.166.148.206) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Jun 2011 13:54:04 +0000 X-Loopcount0: from 10.152.240.141 Subject: Re: Cross debugger Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Paul Koning In-Reply-To: Date: Thu, 16 Jun 2011 13:54:00 -0000 Cc: Content-Transfer-Encoding: quoted-printable Message-Id: <45C23430-D605-4D08-8380-BB4C6C772670@dell.com> References: <20110616025342.GS5944@adacore.com> To: Chris Sutcliffe X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-06/txt/msg00116.txt.bz2 On Jun 16, 2011, at 7:53 AM, Chris Sutcliffe wrote: > On 15 June 2011 22:53, Joel Brobecker wrote: >> What I don't understand is why you created a cross compiler/debugger, >> while it seems to me you could have just created a native x64 MinGW >> toolset. That's what we do at AdaCore: We use cygwin as the build >> environment, but then build a MinGW toolset by configuring with >> --build=3Dx86_64-pc-mingw32. As far as I know, the gdbserver will >> be automatically built. >=20 > Good point, for some reason I was thinking that since gdb would be > running withing the Cygwin environment I would need the > '--host=3Di686-pc-cygwin'. If I build a native x64 MinGW gdb will it > understand Cygwin paths correctly? >=20 >>> (gdb) start >> [...] >>> Don't know how to run. Try "help target". >>=20 >> And that's also expected, since you have a cross-debugger. So the >> debugger is expecting you to connect to the target where the process >> is running. >=20 > Ah, I didn't realize a cross-debugger could only be used to connect to > running process. More precisely, it can attach to an already running process, or you can sta= rt a new one on the command line. Either way, though, by the time gdb conn= ects to gdbserver, the process already exists. If you started it on the co= mmand line, it's on the first instruction (typically some sort of startup l= ibrary code, well before "main"). So either way, you get things going by "= continue". paul