From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.157.12.221 with SMTP id o29mr5580489otd.48.1497809066368; Sun, 18 Jun 2017 11:04:26 -0700 (PDT) X-Received: by 10.157.46.132 with SMTP id w4mr196942ota.18.1497809066342; Sun, 18 Jun 2017 11:04:26 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!2.eu.feeder.erje.net!feeder.erje.net!2.us.feeder.erje.net!weretis.net!feeder6.news.weretis.net!news.glorb.com!185no1562714itv.0!news-out.google.com!s132ni4599itb.0!nntp.google.com!185no1562704itv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 18 Jun 2017 11:04:26 -0700 (PDT) In-Reply-To: <7132e1a3-6c36-4f53-94d5-f51b18373e20@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.166.231.245; posting-account=bPTmZAoAAAC_6HP9XLKB9aAAxBa6BuOR NNTP-Posting-Host: 85.166.231.245 References: <5a0d60e6-c713-4a83-8c98-81a2af68e75e@googlegroups.com> <93822692-767f-4546-8e39-9c4b7ceab3e6@googlegroups.com> <291a8209-d893-4822-896d-32727d5c9509@googlegroups.com> <7132e1a3-6c36-4f53-94d5-f51b18373e20@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <1f3089a8-a304-4be3-ab1d-bff5c5b75a18@googlegroups.com> Subject: Re: Help needed - "Storage_Error stack overflow or erroneous memory access" From: reinert Injection-Date: Sun, 18 Jun 2017 18:04:26 +0000 Content-Type: text/plain; charset="UTF-8" Xref: news.eternal-september.org comp.lang.ada:46988 Date: 2017-06-18T11:04:26-07:00 List-Id: Forgot to say that I changed the hard and soft number of file limits (in the stretch machine) to conform with the "jessie" machine, so now "ulimit -a" gives this (on the "stretch machine"): ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 28417 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65536 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 28417 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited But the problem persists... :-(