From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27841 invoked by alias); 16 Dec 2007 23:48:37 -0000 Received: (qmail 27831 invoked by uid 22791); 16 Dec 2007 23:48:36 -0000 X-Spam-Check-By: sourceware.org Received: from fk-out-0910.google.com (HELO fk-out-0910.google.com) (209.85.128.189) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 16 Dec 2007 23:48:28 +0000 Received: by fk-out-0910.google.com with SMTP id 26so1245040fkx.8 for ; Sun, 16 Dec 2007 15:48:25 -0800 (PST) Received: by 10.78.173.20 with SMTP id v20mr1408227hue.12.1197848905086; Sun, 16 Dec 2007 15:48:25 -0800 (PST) Received: from ?62.169.92.60? ( [62.169.92.60]) by mx.google.com with ESMTPS id h1sm15562084nfh.2007.12.16.15.48.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 16 Dec 2007 15:48:24 -0800 (PST) Message-ID: <4765B945.20404@portugalmail.pt> Date: Sun, 16 Dec 2007 23:48:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: onramp123@yahoo.com CC: gdb@sourceware.org Subject: Re: gdbserver 6.7.1 for mingw32ce connect to host gdb problem References: <009201c84039$0653d510$6603a8c0@sdelaney2> In-Reply-To: <009201c84039$0653d510$6603a8c0@sdelaney2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2007-12/txt/msg00113.txt.bz2 Steve DeLaney wrote: > Good suggestions. comments follow below. > > summary: pilot error on my part. it turns out that gdbserver.exe MUST be > launched like this > gdbserver :9999 /path/test > > and must NOT be launched as I attempted previously: > gdbserver.exe 169.254.2.2:9999 \\path\\test.exe > Well, it depends on what kind of "shell" you use to invoke the command. I was assuming you were invoking from some remote RAPI tool from some shell that needed the escaping, but since you seem to be using MSFT's cmd.exe, you have to use single back-slashes: gdbserver.exe 169.254.2.2:9999 \path\test.exe If that's the case, this is not a gdbserver problem. If it's something else, it could be a bug. > interesting test > b main > c > p argc > $1 = 1 > p argv[0] > $2 = 0x260930 "\\path\test.exe" > > so gdb although invoked with single forward slash,converts to double back > slash. > Actually, it's converted into a single back slash, since that's what the CreateProcess call used to launch the process expects. The double back slash is shown because '\' is the escape char. I guess you have a typo in your example. Glad it's working now. -- Pedro Alves