Closed
Bug 310477
Opened 20 years ago
Closed 20 years ago
nsJavaXPTCStub::CallMethod does incorrect JNI Call<type>MethodA calls
Categories
(Core Graveyard :: Java to XPCOM Bridge, defect)
Core Graveyard
Java to XPCOM Bridge
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhpedemonte, Assigned: jhpedemonte)
Details
(Whiteboard: javaconnect-to-branch)
Attachments
(1 file)
|
1.61 KB,
patch
|
Details | Diff | Splinter Review |
When I changed the Javaconnect code to properly handle unsigned values in Java,
I never changed the Call<type>MethodA calls in nsJavaXPTCStub::CallMethod. Not
sure how I missed that...
| Assignee | ||
Comment 1•20 years ago
|
||
| Assignee | ||
Comment 2•20 years ago
|
||
Checked in to trunk. ->FIXED
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•20 years ago
|
Whiteboard: javaconnect-to-branch
Updated•11 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•