Bug 12026

Summary: ash: -sh not found, no echo
Product: Busybox Reporter: Martijn Scheepers <ms>
Component: OtherAssignee: unassigned
Status: RESOLVED FIXED    
Severity: normal CC: busybox-cvs
Priority: P5    
Version: 1.31.x   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Host: Target:
Build:
Attachments: busybox.config

Description Martijn Scheepers 2019-07-10 09:20:59 UTC
Created attachment 8151 [details]
busybox.config

On a buildroot arm device, busybox ash fails with version 1.31
after login no PS1 line is visable and no chars are echo'd.
typing random chars give
-sh <random chars> not found
busybox internal commands give output
external commands give no output

version 1.30.1 and lower working correct
Comment 1 Denys Vlasenko 2019-07-11 15:08:50 UTC
Can't reproduce - works for me with this config.
Comment 2 spam1 2019-11-07 17:03:20 UTC
I can reproduce it when I try to execute It happens when trying to call shell-builtins from/in PS1:

Working: PS1="\$(date '+%s: ')$PS1"

root@hostname:~# PS1="\$(date '+%s: ')$PS1"
1573146144: root@GARDENA-163008:~#

Hanging: PS1="\$(echo 'MyPrefix ')$PS1"

root@hostname:~# PS1="\$(echo 'MyPrefix ')$PS1"
<hanging>
Comment 3 spam1 2019-11-07 17:05:10 UTC
I can reproduce it when I call shell-builtins from/in PS1:

Working: PS1="\$(date '+%s: ')$PS1"

root@hostname:~# PS1="\$(date '+%s: ')$PS1"
1573146144: root@GARDENA-163008:~#

Hanging: PS1="\$(echo 'MyPrefix ')$PS1"

root@hostname:~# PS1="\$(echo 'MyPrefix ')$PS1"
<hanging>
Comment 4 spam1 2019-11-07 17:05:32 UTC
I can reproduce it when I call shell-builtins from/in PS1:

Working: PS1="\$(date '+%s: ')$PS1"

root@hostname:~# PS1="\$(date '+%s: ')$PS1"
1573146144: root@GARDENA-163008:~#

Hanging: PS1="\$(echo 'MyPrefix ')$PS1"

root@hostname:~# PS1="\$(echo 'MyPrefix ')$PS1"
<hanging>
Comment 5 spam1 2019-11-08 23:33:34 UTC
It seems that this issue has been resolved by commit 943e81f5db56eedbadf43459afbc967d100f9da2 [1] which is part of the 1.31.1 release.

https://git.busybox.net/busybox/commit/?id=943e81f5db56eedbadf43459afbc967d100f9da2
Comment 6 Martijn Scheepers 2019-11-11 12:29:36 UTC
i can confirm that release 1.31.1 fixed the problem.