Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11489

Re: memory hog script crashes bash with segfault

From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: memory hog script crashes bash with segfault
Date 2015-09-11 10:51 -0400
Message-ID <mailman.939.1441983082.19560.bug-bash@gnu.org> (permalink)
References <CALYGNiOfVn-UmZokJ77gRRpbbRwuNNAyAL2Ufnj=+=L7K0Tz=Q@mail.gmail.com> <55F2CEA7.9070404@case.edu> <CALYGNiPVU8nUkc+=eSnAeXik_=subVTey7XSdm0b_KmVKs6oqw@mail.gmail.com>

Show all headers | View raw


On 9/11/15 10:10 AM, Konstantin Khlebnikov wrote:
> On Fri, Sep 11, 2015 at 3:52 PM, Chet Ramey <chet.ramey@case.edu> wrote:
>> On 9/11/15 2:19 AM, Konstantin Khlebnikov wrote:
>>> $ ./bash -c ":(){ : $@$@;};: :"
>>> Segmentation fault
>>
>> This is not a memory allocation problem.  You have defined an infinitely
>> recursive function that, when executed, eventually exceeds your stack size
>> resource limit.  When that happens, the kernel sends a SIGSEGV.
> 
> Yep. But this not happens if command runs in interactive mode.
> Bash uses default stack (with MAP_GROWSDOWN) in interactive mode
> and fixed size stack for "-c" ?

Bash doesn't do anything different.  It may be that your system sets
different resource limits for interactive shells and non-interactive ones.
Either way, it will eventually fail.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: memory hog script crashes bash with segfault Chet Ramey <chet.ramey@case.edu> - 2015-09-11 10:51 -0400

csiph-web