On Fri, Mar 09, 2012 at 08:35:44PM -0000, Loïc Minier wrote:
> In my case, I'm using qemu-arm-static from precise against an unstable Debian armel chroot and that used to work fine but now I get:
> bash: xmalloc: ../bash/variables.c:1969: cannot allocate 28 bytes (24576 bytes allocated)
> when starting bash; if I run "sh" (which is dash) I don't have the problem.
On Fri, Mar 09, 2012 at 08:35:44PM -0000, Loïc Minier wrote: variables. c:1969: cannot allocate 28 bytes (24576 bytes allocated)
> In my case, I'm using qemu-arm-static from precise against an unstable Debian armel chroot and that used to work fine but now I get:
> bash: xmalloc: ../bash/
> when starting bash; if I run "sh" (which is dash) I don't have the problem.
> >From sh, I can reproduce the issue: variables. c:1969: cannot allocate 28 bytes (24576 bytes allocated) armel)root@ bee:~# exit VA=0xf7000000 bash variables. c:2159: cannot allocate 26 bytes (24576 bytes allocated)
> # bash
> bash: xmalloc: ../bash/
> # QEMU_RESERVED_VA=0 bash
> (unstable-
> # QEMU_RESERVED_
> bash: xmalloc: ../bash/
Yes, this is one of the known regressions being discussed upstream, from
what I saw.