Hi,
to deal with the bug no 4389172 from sun~s bug database (description see
below) I need to know
which c++ - compiler was used to compile the blackdown jdk1.3.0.
Was it the gcc ? What was the version of the compiler ?
Were any specific options which have influence on RTTI or exception
handling used for compiling ?
Regards, Markus.
Bug id 4389172
Votes
2
Synopsis
JNI -
Unexpected exception detected in native code outside the VM
Category
java:native_interface
Reported Against
kest-linux-fcs, 1.3
Release Fixed
State
Closed, will
not be fixed
Related Bugs
4407211
Submit Date
Nov 14, 2000
Description
java version
"1.3.0"
Java(TM) 2
Runtime Environment, Standard Edition (build 1.3.0)
Java
HotSpot(TM) Client VM (build 1.3.0, mixed mode)
When
coupling Java and C++ by means of the JNI, I faced the following
problem.
A Java
program calls a native C++ method through the JNI. This C++ method
throws
an exception
and also catches it again. So, the exception does NOT propagate
from the C++
side to the Java side; it remains on the C++ side. Nevertheless,
the JVM
complains about an unexpected exception in the native code.
By the way,
this is not a problem with jdk1.3 in a Solaris environment.
How to
reproduce the problem:
(1) javac
TestExceptions.java
(2) javah
TestExceptions
(3) g++ -o
libtestx.so -fPIC -shared <jni headers> TestExceptions.C
where
<jni headers> is
-I/usr/local/jdk1.3/include -I/usr/local/jdk1.3/include/linux
if you
installed jdk under /usr/local
(4) Prepend
the directory containing libtestx.so (built in step (3))
to the
environment variable LD_LIBRARY_PATH
(5) java
TestExceptions
Faulty
output:
--------------
Boring non-3
MyException
thrown!
# # An
unexpected exception has been detected in native code outside the VM.#
Program
counter=0x406494ea
#
#
Problematic Thread: prio=1 tid=0x804e328 nid=0x66f runnable
#
Correct
output:
---------------
Boring non-3
MyException
thrown!
MyException
caught!
Exceptional
3
Boring non-3
Files:
------
// *** File:
TestExceptions.java ***
public class
TestExceptions {
private
native String threeIsOdd(int number);
static {
System.loadLibrary("testx");
}
public
static void main(String[] args) {
TestExceptions tx = new TestExceptions();
for
(int i = 2; i < 5; i++) {
System.out.println(tx.threeIsOdd(i));
}
}
}
// *** File:
TestExceptions.C ***
#include
<iostream>
#include
"TestExceptions.h"
class
MyException {
public:
MyException() {}
~MyException() {}
};
JNIEXPORT
jstring JNICALL
Java_TestExceptions_threeIsOdd(JNIEnv* env, jobject, jint number)
{
try {
if
(number == 3) {
cout << "MyException thrown!" << endl;
throw MyException();
}
return env->NewStringUTF("Boring non-3");
}
catch
(MyException&) {
cout
<< "MyException caught!" << endl;
return env->NewStringUTF("Exceptional 3");
}
catch
(...) {
cout
<< "OtherException caught!" << endl;
}
return
env->NewStringUTF("Should not be reached");
}
(Review ID:
112220)
webbug
StubertB
Workaround
None.
Evaluation
The JNI
specification makes no guarantees about whether certain C++ language
features,
like C++ exceptions and RTTI, are valid in the context of native
code.
These C++
language features typically require all modules in the system to be
compiled
with the features enabled, and typically require run-time support.
In this case
there is likely poor interaction between gcc's run-time library
and
the host
platform's standard library used by the VM. This is not a problem we
can fix.
xxxxx@xxxxx
2000-12-07
Tried to
reproduce the bug with different environment without success.
Each time
the test case actually works as expected.
System
RedHat 6.2, Mandrake 7.X
egcs1.1.2
and gcc.2.95.2
jdk build
1.3.0, 1.3.0rc1-b17 and latest ladybird integration workspace.
xxxxx@xxxxx
2000-12-07
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
- Re: compiler for jdk1.3 Markus Suing
- Re: compiler for jdk1.3 Juergen Kreileder
- Re: compiler for jdk1.3 Markus Suing
