public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Kiril Vidimce <vkire@pixar.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2397: big char array causes segfault
Date: Wed, 28 Mar 2001 13:16:00 -0000 [thread overview]
Message-ID: <20010328211602.3595.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c/2397; it has been noted by GNATS.
From: Kiril Vidimce <vkire@pixar.com>
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c/2397: big char array causes segfault
Date: Wed, 28 Mar 2001 13:08:42 -0800 (PST)
On 27 Mar 2001 gcc-gnats@gcc.gnu.org wrote:
> Thank you very much for your problem report.
> It has the internal identification `c/2397'.
> The individual assigned to look at your
> report is: unassigned.
I increased the stack limit size with limits and the problem went away.
I am surprised this is a problem though since my stack size limit
was set to 64 MB. Why wasn't this enough?
KV
--
___________________________________________________________________
Studio Tools vkire@pixar.com
Pixar Animation Studios http://www.pixar.com/
next reply other threads:[~2001-03-28 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 13:16 Kiril Vidimce [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-07 14:07 pme
2001-03-26 20:16 Kiril Vidimce
2001-03-26 19:56 vkire
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=20010328211602.3595.qmail@sourceware.cygnus.com \
--to=vkire@pixar.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).