https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #6 from ian at gcc dot gnu.org ian at gcc dot gnu.org ---
Author: ian
Date: Mon Jan 5 16:13:06 2015
New Revision: 219192
URL: https://gcc.gnu.org/viewcvs?rev=219192root=gccview=rev
Log:
PR go/61871
runtime: Increase stack size
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
Uroš Bizjak ubizjak at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #5 from Uroš Bizjak ubizjak at gmail dot com ---
The testcase now fails also on i686-linux-gnu (Fedora 20, x86_64 with -m32):
runtime: memory allocated by OS (0xef4f1000) not in usable range
[0x1820,0x9820)
runtime: out of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #2 from Uroš Bizjak ubizjak at gmail dot com ---
The backtrace mentions malloc/free - deadlock and the segmentation fault
happens later:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x200011d3270 (LWP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #3 from Uroš Bizjak ubizjak at gmail dot com ---
The size in frame #6 is questionable:
#6 0x025a4b30 in __go_new (size=2199032605516) at
/home/uros/gcc-svn/trunk/libgo/runtime/go-new.c:15
(gdb) f 6
#6 0x025a4b30 in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #4 from Uroš Bizjak ubizjak at gmail dot com ---
Following patch fixes the test:
--cut here--
Index: runtime/proc.c
===
--- runtime/proc.c (revision 213681)
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61871
--- Comment #1 from Uroš Bizjak ubizjak at gmail dot com ---
Ops, I was also testing with this patch:
--cut here--
Index: go/regexp/all_test.go
===
--- go/regexp/all_test.go
