[Bug libgcj/15001] New: Using JNI with interpreter and interface methods yields SIGSEGV

[thhal at mailblocks dot com]

When using JNI to call an interpreted method who's jmethodID stems from an
interface, the program receives a SIGSEGV. The signal handler in turn, goes into
an endless unwind loop and the program appears to be hung.

The sample program uses JNI to instantiate the "jvm", obtains the interface and
implementation class, instantiates the latter and tries to call a method on it.
First it uses a jmethodID obtained directly from the implementation class. That
succeeds. Then, it uses the jmethodID it gets when obtaining the same method
from the implemented interface. That fails.

I know that sending a compressed tar file is against your policy, but you do
need the .class files in order to reproduce this bug.

-- 
           Summary: Using JNI with interpreter and interface methods yields
                    SIGSEGV
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: thhal at mailblocks dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
  GCC host triplet: i86-pc-linux-gnu


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