From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26292 invoked by alias); 18 Apr 2006 14:20:19 -0000 Received: (qmail 26283 invoked by uid 22791); 18 Apr 2006 14:20:17 -0000 X-Spam-Check-By: sourceware.org Received: from red.impulse.net (HELO red.impulse.net) (207.154.64.11) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Apr 2006 14:20:14 +0000 Received: from localhost (localhost [127.0.0.1]) by red.impulse.net (Postfix) with ESMTP id 48E731D0F2A; Tue, 18 Apr 2006 07:20:13 -0700 (PDT) Received: from red.impulse.net ([127.0.0.1]) by localhost (red.impulse.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 63210-03-4; Tue, 18 Apr 2006 07:20:09 -0700 (PDT) Received: from [192.168.101.100] (c-67-180-173-103.hsd1.ca.comcast.net [67.180.173.103]) by red.impulse.net (Postfix) with ESMTP id C55811D0FD4; Tue, 18 Apr 2006 07:20:09 -0700 (PDT) In-Reply-To: <001901c662d3$0403feb0$a501a8c0@CAM.ARTIMI.COM> References: <001901c662d3$0403feb0$a501a8c0@CAM.ARTIMI.COM> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <934C7DF3-FA57-48AF-897E-D87517A24572@greeneridge.com> Cc: Content-Transfer-Encoding: 7bit From: Bill Burgess Subject: Re: gdbserver on OS X -- abandon all hope? Date: Tue, 18 Apr 2006 16:17:00 -0000 To: "Dave Korn" X-Mailer: Apple Mail (2.749.3) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00247.txt.bz2 On Apr 18, 2006, at 3:29 AM, Dave Korn wrote: > Sorry, can you just clarify something: if you're cross-compiling > for and > debugging an ARM target, why would you need to configure gdbserver > for OS X? > As far as I understand it you run gdbserver on the target and would > only need > to run plain old gdb itself on your Mac. Wow...I think you are right. I went back and re-read the documentation and it does make more sense when read with your point of view. I had somehow understood that gdb does not have built-in networking code, so that it would need gdbserver to handle networking for it. Sounds silly now doesn't it? If only the documentation had hit me over the head with something like "gdbserver resides on the the remote target" although it does come embarrassingly close to saying just that. Thanks for your response. I've never been so happy to be wrong! --Bill