ash: substring processing seems to be borken
James Simmons
jsimmons at infradead.org
Tue Apr 15 14:51:20 UTC 2008
> On Friday 11 April 2008 16:13, James Simmons wrote:
> >
> > > This one: ${parameter#word}. Can be reproduced with:
> > >
> > > # ./ash -c 'var=1/2/3;echo ${var#?}
> > > 1/2/3
> > >
> > > expected: /2/3.'
> >
> > Did this work before?
>
> It stopped working in revision 21481:
>
> r21481 | vda | 2008-03-25 02:17:40 +0100 (???, 25 ??? 2008) | 17 lines
>
> ash: optional bash-like pattern subst and substring opts
> (by James Simmons <jsimmons AT infradead.org>)
> TODO: write testsuite!
>
> BASH_COMPAT off:
> scanleft 101 262 +161
> subevalvar 346 335 -11
> BASH_COMPAT on:
> subevalvar 346 1397 +1051
> scanleft 101 262 +161
> readtoken1 2739 2807 +68
> cmdputs 397 399 +2
> static.vstype 64 48 -16
> ------------------------------------------------------------------------------
> (add/remove: 0/0 grow/shrink: 4/1 up/down: 1282/-16) Total: 1266 bytes
>
>
> $ bash -c 'var=1/2/3;echo ${var#?}'
> /2/3
>
> $ ./busybox21480 ash -c 'var=1/2/3;echo ${var#?}'
> /2/3
>
> $ ./busybox21481 ash -c 'var=1/2/3;echo ${var#?}'
> 1/2/3
>
> I am attaching my .config and patch which broke ash.
>
> James, can you take a look into it?
I just was testing it. Can you try this. Save your configuration and do a
make mrproper and then rebuild. Then rebuild and try it. When I did this
the problem went away.
More information about the busybox
mailing list