Closed
Bug 82729
Opened 25 years ago
Closed 25 years ago
Blackconnect should not crash mozilla on improper CLASSPATH
Categories
(Core Graveyard :: Java to XPCOM Bridge, defect, P1)
Core Graveyard
Java to XPCOM Bridge
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: edburns, Assigned: blackconnect)
Details
(Keywords: crash)
Attachments
(1 file)
|
3.37 KB,
patch
|
Details | Diff | Splinter Review |
I just built blackconnect for the first time, and after I built it I can no
longer run mozilla without having my CLASSPATH set to mozilla\dist\classes. It
should be the case that mozilla doesn't crash when you have blackconnect
installed AND don't have the proper CLASSPATH.
Basically what I'm saying is, it should fail gracefully.
Comment 2•25 years ago
|
||
Does this affect the m.9.1 trunk build?
| Assignee | ||
Comment 3•25 years ago
|
||
It does not affect the build.
blackConnect is not a part of default build
Status: NEW → ASSIGNED
| Assignee | ||
Comment 4•25 years ago
|
||
| Assignee | ||
Comment 5•25 years ago
|
||
There are two reasons for the browser to crash:
1. No CLASSPATH at all
2. BlackConnect classes are not in the CLASSPATH
Take a look at http://bugzilla.mozilla.org/showattachment.cgi?attach_id=36622
1. No CLASSPATH case served in bcJavaGlobal.cpp.
- added checking for CLASSPATH equal to NULL.
2. Improper CLASSPATH case served in
- bcJavaStubsAndProxies.cpp
added returning NS_ERROR_FAILURE if it could not find blackConnect classes
- bcJavaComponentFactory.cpp
check return value after calling bcJavaStubsAndProxies and fail if it fails
-------------------------------------------
Ed will you please review my patch.
Thanks,
Igor
| Assignee | ||
Comment 7•25 years ago
|
||
checked into the trunk
closed as fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
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
•