public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* c/10127: -fstack-check enforces wrong limit on main thread, works fine on other threads
@ 2003-03-18  0:16 dank
  0 siblings, 0 replies; only message in thread
From: dank @ 2003-03-18  0:16 UTC (permalink / raw)
  To: gcc-gnats


>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@kegel.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:


^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2003-03-18  0:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-18  0:16 c/10127: -fstack-check enforces wrong limit on main thread, works fine on other threads dank

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).