Path: csiph.com!au2pb.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.ripco.com!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Konstantin Khlebnikov <koct9i@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: memory hog script crashes bash with segfault
Date: Fri, 11 Sep 2015 17:10:58 +0300
Lines: 19
Approved: bug-bash@gnu.org
Message-ID: <mailman.937.1441980665.19560.bug-bash@gnu.org>
References: <CALYGNiOfVn-UmZokJ77gRRpbbRwuNNAyAL2Ufnj=+=L7K0Tz=Q@mail.gmail.com> <55F2CEA7.9070404@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: bug-bash@gnu.org
To: chet.ramey@case.edu
Envelope-to: bug-bash@gnu.org
In-Reply-To: <55F2CEA7.9070404@case.edu>
Precedence: list
Xref: csiph.com gnu.bash.bug:11488

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" ?

>
> --
> ``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/