From: Eli Zaretskii <eliz@gnu.org>
To: "Markus Bühren" <bhr2@gmx.de>
Cc: gdb@sourceware.org
Subject: Re: Quotes after --args
Date: Fri, 08 Jun 2012 14:50:00 -0000 [thread overview]
Message-ID: <833965voww.fsf@gnu.org> (raw)
In-Reply-To: <20120608142102.302310@gmx.net>
> Date: Fri, 08 Jun 2012 16:21:02 +0200
> From: "Markus Bühren" <bhr2@gmx.de>
>
> gdb --eval-command=run --batch --args test.exe -f "my testfile.txt"
>
> My program should get two arguments, '-f' and 'my testfile.txt'. However, replacing my actual program test.exe by a program that just prints the input arguments, I get the following result:
>
> C:\>gdb --eval-command=run --batch --args test.exe -f "my testfile.txt"
> [New thread 6180.0xad0]
> argv[0] = >>C:/test.exe<<
> argv[1] = >>-f<<
> argv[2] = >>my\<<
> argv[3] = >>testfile.txt<<
>
> Program exited normally.
>
> Can you help me to avoid that the file name is splitted into two arguments, with replacing the blank ' ' after 'my' by a backslash '\'? I have tried a lot of combinations of double double quotes '""', escaped double quotes '\"' and so on but I did not manage to get the file name passed as a single argument into my program.
It's a bug. GDB handles the whitespace in a way that works on Posix
platforms, but not on Windows.
> PS: Renaming the file is not an option - actually, I already simplified matters here to a file name with a blank in it.
You can always use its 8+3 alias, something like mytest~1.txt (use the
"dir /x" command from the shell prompt to see the actual name),
instead of the long name. This is a workaround, though.
prev parent reply other threads:[~2012-06-08 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1339164112.4081.ezmlm@sourceware.org>
2012-06-08 14:21 ` "Markus Bühren"
2012-06-08 14:50 ` Eli Zaretskii [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=833965voww.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bhr2@gmx.de \
--cc=gdb@sourceware.org \
/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