[Bug libgcj/1373] recursion stress test causes segmentation fault

[Bug libgcj/1373] recursion stress test causes segmentation fault

[aph at gcc dot gnu dot org]

------- Comment #8 from aph at gcc dot gnu dot org  2005-10-13 09:07 -------
See http://gcc.gnu.org/ml/java-patches/2004-q4/msg00230.html.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[aph at gcc dot gnu dot org]

------- Comment #9 from aph at gcc dot gnu dot org  2005-10-13 09:10 -------
See also http://gcc.gnu.org/ml/java-patches/2004-q4/msg00241.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[aph at gcc dot gnu dot org]

------- Comment #10 from aph at gcc dot gnu dot org  2005-10-13 09:11 -------
And http://gcc.gnu.org/ml/java-patches/2004-q4/msg00270.html.

Hans' threading seems to be broken.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[pinskia at gcc dot gnu dot org]

------- Comment #11 from pinskia at gcc dot gnu dot org  2005-11-21 21:46 -------
*** Bug 24980 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vadimn at redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[pinskia at gcc dot gnu dot org]

------- Comment #12 from pinskia at gcc dot gnu dot org  2006-04-23 16:16 -------
*** Bug 27268 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |debian-gcc at lists dot
                   |                            |debian dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[pinskia at gcc dot gnu dot org]

------- Comment #13 from pinskia at gcc dot gnu dot org  2006-04-23 16:18 -------
A better testcase comes from PR 27268 which seg faults at all optimizations
level currently (though this case can also be optimized out to be an infinite
loop really):
public class test
{
    public test()
    {
        test t = new test();
    }

    public static void main(String argv[])
    {
        new test();
    }
}


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-19 15:25 -------
Note at -O1 on the tree-ssa it never exits because of tail recursion optimization also.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2004-01-12 14:41:03         |2004-04-19 15:25:18
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-08 20:44 -------
Note the word "undefined", on most platforms it will work just fine but it does not have to work on 
some platforms or even on ones where  it looks like it does.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[bruno at clisp dot org]

------- Additional Comments From bruno at clisp dot org  2004-01-08 20:39 -------
> One way of fixing this having a signal catcher for SIGSEGV but from the
glibc's signal 
> man page:
> According to POSIX, the behaviour of a process is undefined after it ignores a
SIGFPE, 
> SIGILL, or SIGSEGV signal that was not generated by the kill(2) or the
raise(3) functions.

This is not very relevant, because in practice, using the proper cautions,
catching SIGSEGV coming from a stack overflow works fine. GNU libsigsegv
provides the functionality, and GNU clisp and GNU smalltalk use it. It works on
Linux, OSF/1, FreeBSD, OpenBSD, NetBSD/Alpha, MacOS X, Solaris, HP-UX/HPPA,
IRIX, AIX 4, BeOS, Cygwin, Windows. The only tricky point in using it would be
the necessity to extend the stack by a few pages in order to be able to throw
the StackOverflowException. Or to throw this exception from within the signal
stack. Either of these would be challenging.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373

[Bug libgcj/1373] recursion stress test causes segmentation fault

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-01-07 18:48 -------
A library issue and not a front-end one.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|java                        |libgcj


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1373