Closed Bug 402047 Opened 17 years ago Closed 3 years ago

JNIEnv_ symbols are leaked in libxul

Categories

(Core Graveyard :: Java to XPCOM Bridge, defect)

Other
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: glandium, Unassigned)

Details

I guess this is happening from code in javaxpcom, but functions from JNIEnv_ (in jni.h) end up being visible while they shouldn't, when libxul is built with system wrappers (and not -fvisibility=hidden). It seems logical, though, considering there is a system wrapper for jni.h, making the whole JNIEnv_ struct visible. 00204230 w DF .text 00000031 Base JNIEnv_::CallCharMethod(_jobject*, _jmethodID*, ...) 002041a0 w DF .text 00000030 Base JNIEnv_::CallLongMethod(_jobject*, _jmethodID*, ...) 00200c10 w DF .text 0000002b Base JNIEnv_::NewObject(_jclass*, _jmethodID*, ...) 00204110 w DF .text 0000002e Base JNIEnv_::CallStaticObjectMethod(_jclass*, _jmethodID*, ...) 002071e0 w DF .text 0000002e Base JNIEnv_::CallVoidMethod(_jobject*, _jmethodID*, ...) 00204200 w DF .text 0000002f Base JNIEnv_::CallShortMethod(_jobject*, _jmethodID*, ...) 002041d0 w DF .text 0000002e Base JNIEnv_::CallIntMethod(_jobject*, _jmethodID*, ...) 00204270 w DF .text 00000031 Base JNIEnv_::CallByteMethod(_jobject*, _jmethodID*, ...) 002042b0 w DF .text 00000031 Base JNIEnv_::CallBooleanMethod(_jobject*, _jmethodID*, ...) 002093e0 w DF .text 00000031 Base JNIEnv_::CallStaticBooleanMethod(_jclass*, _jmethodID*, ...) 001ffd70 w DF .text 0000002e Base JNIEnv_::CallObjectMethod(_jobject*, _jmethodID*, ...) 002071b0 w DF .text 0000002e Base JNIEnv_::CallStaticIntMethod(_jclass*, _jmethodID*, ...) 00204170 w DF .text 0000002e Base JNIEnv_::CallFloatMethod(_jobject*, _jmethodID*, ...) 00204140 w DF .text 0000002e Base JNIEnv_::CallDoubleMethod(_jobject*, _jmethodID*, ...) 002040e0 w DF .text 00000030 Base JNIEnv_::CallStaticLongMethod(_jclass*, _jmethodID*, ...)
Assignee: jhpedemonte → nobody
Product: Core → Core Graveyard

Javaxpcom was removed in bug 648593.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.