Re: possible bash bug - 'history'

2013-08-09 Thread Chet Ramey
On 7/19/13 11:23 AM, Mike Fied wrote: > Dear GNU developer/code maintainer, > > Please take a second to take a look at this problem - this might or might > not be a bug, or rather a feature is not implemented in BASH: > I am trying to get the current or "last" command line printed as the result >

memory allocation bug in bash 4.2.39(1)-release

2013-08-09 Thread John Vincent
I'm using bash 4.2.39(1)-release, part of Fedora release 17 (Beefy Miracle) I find that if I enter the command: echo {1..2000} it runs, but afterwards whenever I enter another command I get the error: -bash: fork: Cannot allocate memory I guess that the memory allocated to all those n

Re: memory allocation bug in bash 4.2.39(1)-release

2013-08-09 Thread Bob Proulx
John Vincent wrote: > I find that if I enter the command: > echo {1..2000} > it runs, but afterwards whenever I enter another command I get the error: > -bash: fork: Cannot allocate memory You need to allocate more virtual memory space to your machine. You are asking it to do more than it can