This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
c/10127: -fstack-check enforces wrong limit on main thread, works fine on other threads
- From: dank at kegel dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 18 Mar 2003 00:12:22 -0000
- Subject: c/10127: -fstack-check enforces wrong limit on main thread, works fine on other threads
- Reply-to: dank at kegel dot com
>Number: 10127
>Category: c
>Synopsis: -fstack-check enforces wrong limit on main thread, works fine on other threads
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 18 00:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: dank at kegel dot com
>Release: gcc-2.9x, gcc-3.2
>Organization:
>Environment:
Red Hat 8.0, Pentium 3
>Description:
Compiling the following program with -fstack-check
int main(int argc, char **argv)
{
char foo[2417];
exit(0);
}
yields a SIGSEGV unless you reduce the size of foo below
2417 bytes. See http://www.kegel.com/stackcheck for full
writeup. Workaround is to not use more than 2KB of stack
in the main thread when compiling with -fstack-check.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: