aboutsummaryrefslogtreecommitdiff
path: root/win32
diff options
context:
space:
mode:
authorRon Yorston <rmy@pobox.com>2024-10-06 13:39:09 +0100
committerRon Yorston <rmy@pobox.com>2024-10-06 13:39:09 +0100
commit041f1d29671c58b839c8e63fced7aa901fbade45 (patch)
tree148d9f0a4829981c491743c158450db9290adb05 /win32
parent4c095ae6efd1fa8773a58fb4a1dc79f5810b2369 (diff)
downloadbusybox-w32-041f1d29671c58b839c8e63fced7aa901fbade45.tar.gz
busybox-w32-041f1d29671c58b839c8e63fced7aa901fbade45.tar.bz2
busybox-w32-041f1d29671c58b839c8e63fced7aa901fbade45.zip
ash: fix regression with 'exec sh -s'
It was noted this command didn't work properly: su -t -c 'exec sh -s -c "echo 123"' The child shell performed the 'echo' but then exited, despite the '-s' flag. This is a regression introduced by commit 074ebfca21 (ash: code shrink). This simpler command also failed the same way: sh -c "exec sh -s" This regression dates back even further, to commit da7c8cdf63 (ash: run ash_main() directly from a FS_SHELLEXEC shell). The issue can be avoided if shells invoked by the 'exec' builtin aren't run by calling ash_main() directly. Adds 80-96 bytes. GitHub issue #461.
Diffstat (limited to 'win32')
0 files changed, 0 insertions, 0 deletions