From: "Blair, Charles E III" <c-blair@illinois.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: My arrays in C are too large
Date: Fri, 13 Sep 2019 11:27:00 -0000 [thread overview]
Message-ID: <CY4PR1101MB2133F5567FF267C1DADD000681B30@CY4PR1101MB2133.namprd11.prod.outlook.com> (raw)
I have been using on other machines a program that includes
char *a[50][8192];
but this declaration, by itself, gives "segmentation" errors.
[8192 is BUFSIZ on other machines, although it seems to be 1024 here.
The program uses 50 different permutations on strings of size BUFSIZ.]
-----------------------------------------------------------------------------------
My e-mail system is unreliable. Please write again if you do not receive a reply in a few days. gpg key is available from keyservers.
--
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 reply other threads:[~2019-09-13 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 11:27 Blair, Charles E III [this message]
2019-09-13 12:10 ` 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=CY4PR1101MB2133F5567FF267C1DADD000681B30@CY4PR1101MB2133.namprd11.prod.outlook.com \
--to=c-blair@illinois.edu \
--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).