Closed
Bug 56261
Opened 25 years ago
Closed 25 years ago
proxyEnv->Get<PrimitiveType>ArrayElements(...) always return NULL
Categories
(Core Graveyard :: Java: OJI, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: rpallath, Assigned: joe.chou)
Details
The call proxyEnv->Get<PrimitiveType>ArrayElement in
modules/oji/src/ProxyJNI.cpp always returns null.
The bug is in the Java Plugin code with always returns NULL. A bug has been
filed for the same in SUN Internal bugtraq (ID : 4378653).
When we say proxyEnv->Get<PrimitiveType>ArrayElements(...)
> we actually call the follwoing methods in modules/oji/src/ProxyJNI.cpp file of
Mozilla tree:
>
> #define IMPLEMENT_GET_ARRAY_ELEMENTS(methodName, type) \
> static type* JNICALL methodName(JNIEnv *env, type##Array array, jboolean
*isCopy) \
> { \
> type* outElements = NULL; \ <- note that here it's set to NULL
> ^^^^^^^^^^^^^^^^^^^^^^^^
> nsISecureEnv* secureEnv = GetSecureEnv(env); \
> nsresult result; \
> result = secureEnv->GetArrayElements(type##_type, array, isCopy,
&outElements); \ <- see the code below: outElements never
> changes
>
^^^^^^^^^^^^
> return outElements; <- here we always return NULL to user
> }
(SUN Internal bugtraq ID : 4378653)
In the code section below, outElements may get changed in the function call
below before it is returned to the calling party:
...
result = secureEnv->GetArrayElements(type##_type, array, isCopy, &outElements);
...
Therefore, outElements may not always be null.
Need instructions of how to reproduce the problem.
This does not look like a bug, and I am changing the resolution to invalid till
I hear something different.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
In the java Plugin code (refer to internal SUN Bugtraq Id 4378653) outElements
was never changed. So it was always NULL.
suggessted fix was to change the interface.
But that is not allowed. The bugtraq bug has been closed
Accordingly closing the same
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•