From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21639 invoked by alias); 4 Aug 2006 15:39:23 -0000 Received: (qmail 21631 invoked by uid 22791); 4 Aug 2006 15:39:22 -0000 X-Spam-Check-By: sourceware.org Received: from d102.x-mailer.de (HELO d102.x-mailer.de) (212.162.13.80) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 04 Aug 2006 15:39:20 +0000 Received: from [127.0.0.1] (helo=pasalacqua.de) by d102.x-mailer.de with esmtpa (Exim 4.61) (envelope-from ) id 1G91lc-0004Gx-KN; Fri, 04 Aug 2006 17:39:16 +0200 MIME-Version: 1.0 X-Mailer: X-Mailer 1.51 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <20060802030320.GA981@nevyn.them.org> References: <20060728160749.GA18728@nevyn.them.org> <20060729141300.B6A964B269@return.false.org> <20060802030320.GA981@nevyn.them.org> Date: Fri, 04 Aug 2006 15:39:00 -0000 From: "Sascha" To: 'Daniel Jacobowitz' Cc: gdb@sourceware.org Subject: Re: Interested in remote protocol improvements X-Info: valid message X-Info: original Date 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-08/txt/msg00025.txt.bz2 > I rewrote a bunch of the native Windows support code after our last release. > I bet that would help you with your networking performance problems. > None of that code is on the branch; it's only available on the FSF > HEAD, which doesn't have the XML description stuff yet. > It might be a general Windows issue... but that would be pretty > disappointing. If it is, there's not much we can do about it :-( > You might want to try communicating with the stub over a pipe instead > of a TCP socket; that's what we've been doing recently here at > CodeSourcery. Somehow I feel that this is a Win32 issue, but I haven't found any information about this (Maybe you (or someone else) can run the "while++ < 10000" test on windows using mingw gdb and gdbserver to verify this? ) I already noticed that there is a pipe support implemented for gdb/mingw - is that what you are using ? Unfortunately there is no documentation. I had a look at the source and did a test but GDB wants to launch another application if I specify the "|" to use a pipe (target remote | something). My stub is already running and it would use the named pipe api. Does gdb support named pipes ? > Gdbserver didn't used to be available, but it is now. You can build it > from the latest FSF HEAD snapshots; Alright. Good to know. Another question about the remote protocol... the error code numbers don't have any effect, do they ? If my stub responds with "E99" for example, how do I notice this (number) in GDB ? And even more important, how do I notice this using GDB/MI ? Thanks