[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #28934] execve(path, args) should take path as a a relative path if
Emilio Pozuelo Monfort
[bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes
Sun, 21 Mar 2010 18:28:35 +0000
Mozilla/5.0 (X11; U; Linux i686; es-es) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+ Debian/squeeze/sid () Epiphany/2.29.92
Follow-up Comment #7, bug #28934 (project hurd):
The attached two patches fix this by adding a new exec flag in Hurd,
EXEC_FILE_NAME, that will make the exec server to not look at PATH, but just
exec the name it's been passed, even if it doesn't contain slashes.
Then we add a new _hurd_exec_file_name() that will use EXEC_FILE_NAME.
I didn't think a lot about the new function name, but it would be possible to
change it or to deprecate _hurd_exec and create a new one that has a flags
arguments (to not have two different ones) or whatever.
I've tested the patches, they fix the bug and I haven't noticed any
(file #19993, file #19994)
Additional Item Attachment:
File name: hurd.patch Size:1 KB
File name: glibc.patch Size:2 KB
Reply to this item at:
Message sent via/by Savannah
- [bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes,
Emilio Pozuelo Monfort <=