On Sat, Oct 29, 2016 at 8:22 PM, Harald van Dijk wrote:
> On 28/10/16 15:55, Denys Vlasenko wrote:
>>
>> This will probably be mangled by gmail, but here is the proposed fix:
>
>
> This looks about the right approach, but it causes problems in subshells, a
> double free:
>
> $ ./busybox ash -c 're
On 28/10/16 15:55, Denys Vlasenko wrote:
This will probably be mangled by gmail, but here is the proposed fix:
This looks about the right approach, but it causes problems in
subshells, a double free:
$ ./busybox ash -c 'readonly x; echo $(command eval x=2)'
ash: eval: line 1: x: is read only
This will probably be mangled by gmail, but here is the proposed fix:
Date: Fri, 28 Oct 2016 15:43:50 +0200
Subject: [PATCH] ash: fix interactive "command eval STRING" exiting on errors.
This bug is also present in current dash
Signed-off-by: Denys Vlasenko
---
shell/ash.c
