Bug 39306 - -fstack-check + large frame == SIGSEGV
Summary: -fstack-check + large frame == SIGSEGV
Status: RESOLVED DUPLICATE of bug 13757
Alias: None
Product: gcc
Classification: Unclassified
Component: middle-end (show other bugs)
Version: 4.4.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 17:47 UTC by Paul Pluzhnikov
Modified: 2009-02-26 08:16 UTC (History)
3 users (show)

See Also:
Host: i686-unknown-linux-gnu
Target: i686-unknown-linux-gnu
Build: i686-unknown-linux-gnu
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Pluzhnikov 2009-02-25 17:47:38 UTC
Discovered as a failure of GDB test:
FAIL: gdb.base/stack-checking.exp: continue to breakpoint: breakpoint for big frame

With current SVN head @144426:

/* t.c */
void foo() { char buf[524188]; }
int main() { foo(); return 0; }

i686-unknown-linux-gnu-gcc t.c -fstack-check && ./a.out
Segmentation fault

AFAICT, this is a regression from 4.3.1
Problem also happens in x86_64-unknown-linux-gnu.
Minimal size to crash appears to be about 57058.
Comment 1 Andrew Pinski 2009-02-25 17:56:14 UTC
fstack-check  is known to be broken on x86 GNU/Linux, see PR 13757.

So I don't think this is a regression even.
Comment 2 Eric Botcazou 2009-02-26 08:16:51 UTC
> fstack-check  is known to be broken on x86 GNU/Linux, see PR 13757.

Yes, the current implementation is non-functional on x86{-64}/Linux.


*** This bug has been marked as a duplicate of 13757 ***