public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ludovic dot brenta at insalien dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/20075] Bug in GNAT.Expect.Non_Blocking_Spawn
Date: Sun, 20 Feb 2005 23:07:00 -0000	[thread overview]
Message-ID: <20050220171447.27481.qmail@sourceware.org> (raw)
In-Reply-To: <20050219113933.20075.sbellon@sbellon.de>


------- Additional Comments From ludovic dot brenta at insalien dot org  2005-02-20 17:14 -------
Hi Stefan,

I've given some more thought to the problem, and I think that perhaps
the bug is in Ada.Command_Line.Command_Name, not in GNAT.OS_Lib or
GNAT.Expect.  Indeed, it is Ada.Command_Line.Command_Name that
truncates argv[0] at the first space, isn't it?  And this is wrong,
because even the basename of the program may have spaces in it.

To demonstrate this, I renamed "show_params" to "show params" and
amended launcher.adb accordingly:

$ gnatmake -o "show params" show_params.adb
$ gnatmake launcher.adb
$ PATH=$(pwd) ./launcher
via GNAT.OS_Lib.Spawn:
show params
via GNAT.Expect.Non_Blocking_Spawn:
/home/lbrenta/src/ada/tmp/ada 20075/show params

Could you try that on Windows in a path that does not have a space in
it (e.g. "C:\Temp\show params.exe")?

-- 
Ludovic Brenta.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ludovic dot brenta at
                   |                            |insalien dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20075


  reply	other threads:[~2005-02-20 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 18:27 [Bug ada/20075] New: " sbellon at sbellon dot de
2005-02-20 23:07 ` ludovic dot brenta at insalien dot org [this message]
2005-02-21  2:01 ` [Bug ada/20075] " sbellon at sbellon dot de
2005-02-28  2:52 ` sbellon at sbellon dot de
2005-09-01 11:45 ` charlet at gcc dot gnu dot org
2005-09-01 11:47 ` charlet at gcc dot gnu dot org

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=20050220171447.27481.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).