[gccsdk] [Bug 222] exec() functions and single/double quotes in arguments

bugzilla-daemon at riscos.info bugzilla-daemon at riscos.info
Wed Sep 7 16:00:13 PDT 2011


http://www.riscos.info/bugzilla3/show_bug.cgi?id=222

John Tytgat <John.Tytgat at aaug.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from John Tytgat <John.Tytgat at aaug.net> 2011-09-07 16:00:13 PDT ---
I don't think this can be reasonably solved without causing regressions
elsewhere.

Under RISC OS we don't have a shell which resolves quotes and backslashes like
it is happening with Unix shells.  So UnixLib based programs need to un-quote
(and un-backslash) their own process arguments like an Unix shell would be
doing (cfr code in unix/unix.c).  And if an UnixLib based program is calling
execvp(), it needs to quote & backslash its arguments.  However, if the
process/command specified in execvp() is a non-UnixLib based program (like a
RISC OS command) this is not wanted (like this bug report is demonstrating). 
The problem is that UnixLib doesn't know if the execvp() spawned process is
going to be an UnixLib based process or not, at least that's a non-trivial task
to figure out.

-- 
Configure bugmail: http://www.riscos.info/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.




More information about the gcc mailing list