From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: My C arrays are too large
Date: Fri, 13 Sep 2019 18:44:00 -0000 [thread overview]
Message-ID: <87ftl0jb1i.fsf@Rainer.invalid> (raw)
In-Reply-To: <CY4PR1101MB21339312E8F5656D8C887BFE81B30@CY4PR1101MB2133.namprd11.prod.outlook.com> (Charles E. Blair, III's message of "Fri, 13 Sep 2019 12:10:47 +0000")
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
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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
next prev parent reply other threads:[~2019-09-13 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 12:18 Blair, Charles E III
2019-09-13 12:37 ` Eliot Moss
2019-09-13 18:44 ` Achim Gratz [this message]
2019-09-13 18:50 ` Eliot Moss
2019-09-13 19:01 ` Jose Isaias Cabrera
2019-09-14 5:32 ` Lee
2019-09-18 19:09 ` Joel Rees
2019-09-18 20:40 ` Jose Isaias Cabrera
2019-09-18 20:46 ` Eliot Moss
2019-09-19 1:19 ` Joel Rees
2019-09-19 18:04 ` Jose Isaias Cabrera
2019-09-19 21:58 ` Brian Inglis
2019-09-13 13:44 my " Blair, Charles E III
2019-09-13 14:20 ` Eliot Moss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftl0jb1i.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).