[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
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: |
Mon, 12 Apr 2010 08:40:13 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; es-es) AppleWebKit/531.2+ (KHTML, like Gecko) Safari/531.2+ Debian/squeeze/sid () Epiphany/2.30.2 |
Follow-up Comment #10, bug #28934 (project hurd):
Err the glibc patch was not the one I finally used (I attached the wrong
one). Here's the one I've used. I've tested in another VM and I see the same
regression.
Furthermore I've found that gcc stops working fine in a machine with a new
glibc.so and /hurd/exec (building my testcase fails because gcc can't find
stddef.h), but that may be a consequence of the previous regression I
mentioned.
It's indeed weird that it affects ELF binaries. I've looked if I could find
something weird with the flags argument but everything looks right to me.
I'll try to debug the exec server with gdb to see what's going on. If you
want to try this out, you can find the exec binary and libc.so on
strauss.debian.net, on /home/pochu
(file #20202)
_______________________________________________________
Additional Item Attachment:
File name: glibc.patch Size:2 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28934>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #28934] execve(path, args) should take path as a a relative path if it doesn't contain slashes,
Emilio Pozuelo Monfort <=