This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/10260] alloca 0xFFFFFFFF and -fstack-check
- From: "user42 at zip dot com dot au" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Dec 2003 20:46:55 -0000
- Subject: [Bug other/10260] alloca 0xFFFFFFFF and -fstack-check
- References: <20030329003600.10260.user42@zip.com.au>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From user42 at zip dot com dot au 2003-12-02 20:46 -------
Subject: Re: alloca 0xFFFFFFFF and -fstack-check
"pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
>
> What is really funny when run under gdb, it does not segfault which
> means the code produced b gcc is right.
>
> Status|NEW |RESOLVED
> Resolution| |INVALID
No, the point of my report was that I believe under -fstack-check an
alloca as described is _supposed_ to fault.
If you find it doesn't fault then that's confirmation, not refutation
:-).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10260