|
From: | Emilio Pozuelo Monfort |
Subject: | [bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes |
Date: | Fri, 26 Feb 2010 11:37:44 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; es-es) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+ Epiphany/2.29.90.1 |
Follow-up Comment #3, bug #28934 (project hurd): Hi Carl, Actually I don't think the exec server needs to know what exec*() variant has been called, since the call itself will have called execve() with the full path by looking at PATH if needed (see glibc's posix/execvpe.c, the beginning of the do-while() loop around line 140). Anyway since that may be an implementation detail and since I don't know if changing the exec server to stop looking at $PATH if the file doesn't contain an slash will break other stuff, changing execve() as you propose sounds like a good idea. Another similar option is to prepend . to $PATH in that case (and then the exec server will prepend ./ to the file). I'm going to prepare and test a patch for one of the two options. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?28934> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |