[Bug 4135] Error running some shell scripts directly
bugzilla at busybox.net
bugzilla at busybox.net
Fri Sep 16 08:43:52 UTC 2011
https://bugs.busybox.net/show_bug.cgi?id=4135
--- Comment #6 from Denys Vlasenko <vda.linux at googlemail.com> ---
>From your .config:
CONFIG_BUSYBOX_EXEC_PATH="./dist"
which looks wrong to me. It's usually "/proc/self/exe", "/bin/busybox" or
similar. Why did you set it to "./dist"? I mean, it's a _relative_ path!?
>From LOG:
10634 20:13:23.989951 execve("./bar", ["./bar"], [/* 43 vars */]) = -1 ENOEXEC
(Exec format error)
Now ash tries to exec itself... using CONFIG_BUSYBOX_EXEC_PATH:
10634 20:13:23.990113 execve("./dist", ["ash", "./bar"], [/* 43 vars */]) = -1
ENOENT (No such file or directory)
and not surprisingly, "./dist" doesn't exist, and execve fails.
10634 20:13:23.990262 write(2, "./foo.sh: "..., 10) = 10
10634 20:13:23.990312 write(2, "line 4: "..., 8) = 8
10634 20:13:23.990361 write(2, "./bar: not found"..., 16) = 16
10634 20:13:23.990414 write(2, "\n"..., 1) = 1
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list