DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=IBIFnPc
	KXVmzSx53QXhEOi14DKgAVlkoxzw/F/+XQsx9HshzzFx2yOHEQuVZsvb7NFuiymW
	GCTi9ndOlHDbAzv+YQDcaGMOgmCqGcAD6UbDRNriT/uCEc72NhacKdLlHfHLHY3I
	RNPknFjOaZZ9Hzy5di7zFvksBFffo1KCKrrI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <VI1PR01MB44132EB2432CCD4CE1892304DEB30@VI1PR01MB4413.eurprd01.prod.exchangelabs.com>
References: <CY4PR1101MB21339312E8F5656D8C887BFE81B30@CY4PR1101MB2133.namprd11.prod.outlook.com> <87ftl0jb1i.fsf@Rainer.invalid> <VI1PR01MB44132EB2432CCD4CE1892304DEB30@VI1PR01MB4413.eurprd01.prod.exchangelabs.com>
From: Lee <ler762@gmail.com>
Date: Fri, 13 Sep 2019 19:05:38 -0400
Message-ID: <CAD8GWsu80Fd7edqaC5GYZnFvkjUGdtxd6Lpg9t_WJ-uUoCv_mA@mail.gmail.com>
Subject: Re: My C arrays are too large
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On 9/13/19, Jose Isaias Cabrera wrote:
>
> Achim Gratz, on Friday, September 13, 2019 02:39 PM, wrote...
>>
>> Blair, Charles E III writes:
>> > My apologies for failing to reply on-list.  I don't know how :(
>> >
>> > My machine is 64 bit, and I hope I installed the correct version of
>> > cygwin.
>> >
>> > This program:
>> >
>> > #include<stdio.h>
>> > int main(){char *a[50][8192];
>> > return 0;}
>> >
>> > compiles with gcc  (no special options) but gives "Segmentation fault".
>>
>> You are creating an automatic variable that's larger than the default
>> stack.  You need to enlarge the stack, either during link time or later
>> e.g. via
>>
>> peflags -x0x800000 a.out
>
> This is great! Thanks.
>
> But, let's talk about this a bit... Shouldn't the compiler provide some
> warning, and also, it should never blow up with a "Segmentation fault".  I
> believe there should be some type of Out Of Memory error, or something like
> it.  But now just blow up.  Anyone thinks like me?  Just my 102 Dominican
> cents ($1 = $51 Dominican). :-)

Yes, it would be nice if you got an error message.  But once you
notice a .stackdump file has magically appeared, then
$ gcc -o a.exe starray.c

$ ./a
Segmentation fault (core dumped)

$ cat a.exe.stackdump
Exception: STATUS_STACK_OVERFLOW at rip=001004010C6
  <.. snip ..>

Search for "cygwin STATUS_STACK_OVERFLOW" and find
  https://github.com/OpenFAST/openfast/issues/144

which gives you
$ gcc -o a.exe -Wl,--stack,0x1000000 starray.c

$ ./a

$ peflags -x a.exe
a.exe: stack reserve size      : 16777216 (0x1000000) bytes

Regards,
Lee

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple