Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: onramp123@yahoo.com
Cc: gdb@sourceware.org
Subject: Re: gdbserver 6.7.1 for mingw32ce connect to host gdb problem
Date: Sun, 16 Dec 2007 23:48:00 -0000	[thread overview]
Message-ID: <4765B945.20404@portugalmail.pt> (raw)
In-Reply-To: <009201c84039$0653d510$6603a8c0@sdelaney2>

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


      reply	other threads:[~2007-12-16 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15 15:44 Steve DeLaney
2007-12-16 16:41 ` Pedro Alves
2007-12-16 23:14   ` Steve DeLaney
2007-12-16 23:48     ` Pedro Alves [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4765B945.20404@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=gdb@sourceware.org \
    --cc=onramp123@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox