This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c/2397: big char array causes segfault
- To: nobody at gcc dot gnu dot org
- Subject: Re: c/2397: big char array causes segfault
- From: Kiril Vidimce <vkire at pixar dot com>
- Date: 27 Mar 2001 04:16:01 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Kiril Vidimce <vkire at pixar dot com>
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: Mon, 26 Mar 2001 20:13:58 -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.
>
> >Category: c
> >Responsible: unassigned
> >Synopsis: big char array causes segfault
> >Arrival-Date: Mon Mar 26 19:56:00 PST 2001
I guess it has nothing to do with the type. It seems like a stack
overflow. Is there an option in gcc to add a check before each stack
allocation? I couldn't find one in the man page.
Thanks,
KV